[
https://issues.apache.org/jira/browse/LUCENE-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747587#action_12747587
]
Tim Smith commented on LUCENE-1849:
-----------------------------------
bq. I would prefer not to make a default here, ie, force an explicit choice,
because it is an expert API.
very reasonable
bq. BooleanQuery gets sizable gains in performance if you let it return docs
out of order.
Any stats on the performance gains here available?
didn't see any on a cursory glance through javadoc
Also, are the implications of out of order docids coming back from nextDoc()
well documented (javadoc?, wiki?)?
I guess out of order docids really screw up advance(int), so you should never
call advance(int) if you allowed out of order collection for a Scorer?
> Add OutOfOrderCollector and InOrderCollector subclasses of Collector
> --------------------------------------------------------------------
>
> Key: LUCENE-1849
> URL: https://issues.apache.org/jira/browse/LUCENE-1849
> Project: Lucene - Java
> Issue Type: Wish
> Components: Search
> Affects Versions: 2.9
> Reporter: Tim Smith
> Priority: Minor
> Fix For: 2.9
>
>
> I find myself always having to implement these methods, and i always return a
> constant (depending on if the collector can handle out of order hits)
> would be nice for these two convenience abstract classes to exist that
> implemented acceptsDocsOutOfOrder() as final and returned the appropriate
> value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
