[
https://issues.apache.org/jira/browse/LUCENE-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601428#comment-14601428
]
Adrien Grand commented on LUCENE-6601:
--------------------------------------
The contract of the Query API is that you first need to call rewrite as long as
rewrite returns a different query (see IndexSearcher.rewrite), and this will
give you a Query that supports createWeight. So in this particular case, I
think we just need to make sure to call rewrite first? I already committed such
a change and it makes the test pass, please let me know if it somehow changes
the behaviour of this HashQParser in an undesired way?
> Change FilteredQuery.FilterStrategy to use the two-phase iteration API
> ----------------------------------------------------------------------
>
> Key: LUCENE-6601
> URL: https://issues.apache.org/jira/browse/LUCENE-6601
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Fix For: 5.3
>
> Attachments: LUCENE-6601.patch
>
>
> We could change FilterStrategy so that instead of being a factory of scorers,
> it would just rewrite filters in such a way that they can decide which of the
> iterator or random-access API should be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
