cfd22cd493
group.query after execution forms QueryCommandResult. In case of group.main=true or group.format=simple, QueryCommandResult was not consumed in EndResultTransformer. Also, MainEndResultTransformer assumed that always group.field would be specified. When group.field not specified it failed with AIOOBE. After adding suppport for QueryCommandResult in EndResultTransformers and handling AIOOBE, group.query started giving results Working on tests exposed few other issues. Results differed b/w standalone & distributed mode. * One of the reason is that TopGroupShardResponseProcessor doesn't consider correct limit and offset when group format is simple. In case of simple, start and rows should be used as limit and offset instead of group.limit and group.offset. * Secondly, In distributed second phase grouping, computing docsToCollect didn't consider group response format. This issue is again similar to above issue * offset(group.offset or start) not being considered during TopDocs#merge caused different results. The fix was to use to offset in merge process * group.offset doesn't support negative values but there is no checks on the value. In case of negative values AIOOBE. Now, checks are added for negative values and returns proper error message(this change is for both standalone and distrbuted). Validation is done only in case of group.format=grouped as that is only case when group.offset is consumed. Fixing above issues resolved the differences b/w standalone and distributed mode.
Apache Lucene and Solr
Apache Lucene is a high-performance, full featured text search engine library written in Java.
Apache Solr is an enterprise search platform written using Apache Lucene. Major features include full-text search, index replication and sharding, and result faceting and highlighting.
Online Documentation
This README file only contains basic setup instructions. For more comprehensive documentation, visit:
Building Lucene/Solr
(You do not need to do this if you downloaded a pre-built package.)
Lucene and Solr are built using Apache Ant. To build Lucene and Solr, run:
ant compile
If you see an error about Ivy missing while invoking Ant (e.g., .ant/lib does not exist), run ant ivy-bootstrap and retry.
Sometimes you may face issues with Ivy (e.g., an incompletely downloaded artifact). Cleaning up the Ivy cache and retrying is a workaround for most of such issues:
rm -rf ~/.ivy2/cache
The Solr server can then be packaged and prepared for startup by running the
following command from the solr/ directory:
ant server
Running Solr
After building Solr, the server can be started using
the bin/solr control scripts. Solr can be run in either standalone or
distributed (SolrCloud mode).
To run Solr in standalone mode, run the following command from the solr/
directory:
bin/solr start
To run Solr in SolrCloud mode, run the following command from the solr/
directory:
bin/solr start -c
The bin/solr control script allows heavy modification of the started Solr.
Common options are described in some detail in solr/README.txt. For an
exhaustive treatment of options, run bin/solr start -h from the solr/
directory.
Development/IDEs
Ant can be used to generate project files compatible with most common IDEs. Run the ant command corresponding to your IDE of choice before attempting to import Lucene/Solr.
- Eclipse -
ant eclipse(See this for details) - IntelliJ -
ant idea(See this for details) - Netbeans -
ant netbeans(See this for details)
Running Tests
The standard test suite can be run with the command:
ant test
Like Solr itself, the test-running can be customized or tailored in a number or ways. For an exhaustive discussion of the options available, run:
ant test-help
Contributing
Please review the Contributing to Solr Guide for information on contributing.
Discussion and Support
- Users Mailing List
- Developers Mailing List
- Lucene Issue Tracker
- Solr Issue Tracker
- IRC:
#solrand#solr-devon freenode.net