[
https://issues.apache.org/jira/browse/LUCENE-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117352#comment-13117352
]
Robert Muir commented on LUCENE-3474:
-------------------------------------
No, I think the scorercontext was geared at us being able to make changes
without breaking the API: After
Mike's comment the more I think about it I think this was a bad idea... its
being used here like Solr's NamedList
hammer...
I think we should keep type safety on the Q/W/S apis to avoid traps... adding
Bits like this to a ScorerContext
is a great example where we 'break backwards compatibility' in a sneaky way...
far better to have a compile break.
So, +1 to go nuclear on ScorerContext completely.
> pass liveDocs Bits down in scorercontext, instead of Weights pulling from the
> reader
> -------------------------------------------------------------------------------------
>
> Key: LUCENE-3474
> URL: https://issues.apache.org/jira/browse/LUCENE-3474
> Project: Lucene - Java
> Issue Type: Task
> Affects Versions: 4.0
> Reporter: Robert Muir
> Assignee: Robert Muir
> Attachments: LUCENE-3474.patch, LUCENE-3474.patch
>
>
> Spinoff from LUCENE-1536, this would allow filters to work in a more flexible
> way (besides just cleaning up)
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
