[
https://issues.apache.org/jira/browse/LUCENE-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662791#action_12662791
]
Uwe Schindler commented on LUCENE-1517:
---------------------------------------
In principle, yes!
In relation to my latest contribution to LUCENE-1345, this may be removed in
future when Queries and Filters get the same! But for easier understanding the
term of "TrieRangeQuery" should be kept.
> Change superclass of TrieRangeQuery
> -----------------------------------
>
> Key: LUCENE-1517
> URL: https://issues.apache.org/jira/browse/LUCENE-1517
> Project: Lucene - Java
> Issue Type: Improvement
> Components: contrib/*
> Affects Versions: 2.9
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 2.9
>
> Attachments: LUCENE-1517.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> This patch changes the superclass of TrieRangeQuery to ConstantScoreQuery.
> The current implementation is using rewrite() and was copied from early
> RangeQueries. But this is not needed, the TrieRangeQuery can easily
> subclassed from ConstantScoreQuery.
> If LUCENE-1345 is solved, the whole TrieRangeQuery can be removed, as
> TrieRangeFilter can be added to BooleanQueries. The whole TrieRangeQuery
> class is just a convenience class for easier usage of the trie contrib.
--
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: [email protected]
For additional commands, e-mail: [email protected]
