[
https://issues.apache.org/jira/browse/LUCENE-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747427#action_12747427
]
Yonik Seeley commented on LUCENE-1849:
--------------------------------------
bq. I think we should simply do nothing. This is an expert API.
+1
The reality is that order will matter for some custom collectors, and the
abstract method makes that clear.
The API is fine as it is, but if we wanted to provide a default in Collector,
that would be fine too.
*If* we were to provide a default in Collector, it should be a simple constant,
not a variable. Subclasses changing would simply override the method as
normal. We should strive to treat our abstract base classes as interfaces, and
adding fields and final methods should be avoided.
> 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
