[
https://issues.apache.org/jira/browse/LUCENE-6301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-6301:
---------------------------------
Attachment: LUCENE-6301.patch
Here is a patch:
- Filter, QueryWrapperFilter and FilteredQuery are deprecated
- lucene/core is Filter-free (the only last occurrences are in tests to make
sure the deprecated classes still work)
The only thing that prevents us from removing FilteredQuery is lucene/spatial
which has filters that only support random-access:
{noformat}
@Override
public DocIdSetIterator iterator() throws IOException {
throw new UnsupportedOperationException(
"Iteration is too slow; instead try
FilteredQuery.QUERY_FIRST_FILTER_STRATEGY");
//Note that if you're truly bent on doing this, then see
FunctionValues.getRangeScorer
}
{noformat}
But it should be possible to migrate it to two-phase approximations and having
FilteredQuery deprecated in the meantime will help ensure no new code is using
it. I don't think it should hold this issue as having filters removed from the
core is already a good step towards removing filters entirely?
> Deprecate Filter
> ----------------
>
> Key: LUCENE-6301
> URL: https://issues.apache.org/jira/browse/LUCENE-6301
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Fix For: Trunk, 5.1
>
> Attachments: LUCENE-6301.patch
>
>
> It will still take time to completely remove Filter, but I think we should
> start deprecating it now to state our intention and encourage users to move
> to queries as soon as possible?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
