|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
It is possible that several Queries are more efficient with Lucene 4.x but it's worth keeping in mind that all "native" queries in Lucene are no more than a Java-coded Collector. Just saying that whatever you expect to do in a native query can be done in Search as well coding a custom Collector.
The API in Lucene 4 changes a bit, so it is correct to say that it might be worth doing the migration first and exploring more custom collectors later.
Implementation - wise I would expect you to run the filtering first, so to exclude all results out of range, and only then apply custom scoring on the results.