[
https://issues.apache.org/jira/browse/LUCENE-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117334#comment-13117334
]
Robert Muir commented on LUCENE-3474:
-------------------------------------
{quote}
Failing that.... another option would be to just stop using an object
here at all, and go back to passing explicit flags down to
Weight.scorer.
{quote}
This is interesting for discussion too: because a compile-time break is
"better" than a runtime break I think in cases of changes to
query/weight/scorer?
Like we can look at a compile-time-break as a feature: if we add a new thing
(e.g. imagine adding this bitset after the fact), its crap for us to say 'but
we didnt break backwards compatibility' when in fact you really do need to
change your code!
> 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]
