[
https://issues.apache.org/jira/browse/LUCENE-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698784#action_12698784
]
Uwe Schindler commented on LUCENE-1602:
---------------------------------------
An additional extension to MultiTermQuery:
The original version of TrieRange had a shortcut in the getDocIdSet call: If
the range was inverse and would return for sure no documents, it returned the
DocIdSet.EMPTY_DOCID_SET instance and did not allocate any OpenBitSet.
MultiTermQuery could also do this automatically, if the FilteredTermEnum is
empty from the beginning (simple check before allocating the bitset). This
would be a nice memory-friendly imporvement. I could try to implement this in
MultiTermQuery's getDocIdSet().
> Rewrite TrieRange to use MultiTermQuery
> ---------------------------------------
>
> Key: LUCENE-1602
> URL: https://issues.apache.org/jira/browse/LUCENE-1602
> Project: Lucene - Java
> Issue Type: New Feature
> Components: contrib/*
> Affects Versions: 2.9
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 2.9
>
> Attachments: LUCENE-1602.patch
>
>
> Issue for discussion here:
> http://www.lucidimagination.com/search/document/46a548a79ae9c809/move_trierange_to_core_module_and_integration_issues
> This patch is a rewrite of TrieRange using MultiTermQuery like all other core
> queries. This should make TrieRange identical in functionality to core range
> queries.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
