[jira] [Updated] (JCR-3091) Lucene Scorer implementations should handle the 'advance' to NO_MORE_DOCS optimisation better

["Alex Parvulescu (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Parvulescu updated JCR-3091:
---------------------------------

    Attachment: JCR-3091.patch

attached patch to update all scorers.

feedback?
                
> Lucene Scorer implementations should handle the 'advance' to NO_MORE_DOCS optimisation better
> ---------------------------------------------------------------------------------------------
>
>                 Key: JCR-3091
>                 URL: https://issues.apache.org/jira/browse/JCR-3091
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>         Attachments: JCR-3091.patch
>
>
> This is from the lucene Scorer (actually DocIdSetIterator) api:
> "NOTE: this method may be called with NO_MORE_DOCS for efficiency by some Scorers. If your implementation cannot efficiently determine that it should exhaust, it is recommended that you check for that value in each call to this method."
> None of the scorer implementations does that currently. Except for ChildAxisScorer thanks to JCR-3082.
> This is a worthwhile effort, which can save us from bugs (JCR-3082) but also leverage some performance optimisation hints from the lucene api.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira