[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725588#action_12725588
]
Shalin Shekhar Mangar commented on SOLR-940:
--------------------------------------------
{quote}
the reason was, that all other range filters in lucene core do not allow this.
{quote}
If you look at RangeQuery constructor, it creates a new Term instance (even for
null lower and upper) so an open ended search executes fine.
{quote}In general one should use a MatchAllDocsQuery in this case, as it is
more performant{quote}
But a MatchAllDocsQuery is not equivalent to this when some documents do not
have a value for this field. For example, fq=*:* AND -f:[* TO *] will match
all documents which do not have a value for field f.
> TrieRange support
> -----------------
>
> Key: SOLR-940
> URL: https://issues.apache.org/jira/browse/SOLR-940
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Assignee: Shalin Shekhar Mangar
> Fix For: 1.4
>
> Attachments: SOLR-940-LUCENE-1602.patch, SOLR-940-LUCENE-1602.patch,
> SOLR-940-LUCENE-1701.patch, SOLR-940-newTrieAPI.patch,
> SOLR-940-newTrieAPI.patch, SOLR-940-rangequery.patch,
> SOLR-940-rangequery.patch, SOLR-940-test.patch, SOLR-940.patch,
> SOLR-940.patch, SOLR-940.patch, SOLR-940.patch, SOLR-940.patch,
> SOLR-940.patch, SOLR-940.patch, SOLR-940.patch, SOLR-940.patch, SOLR-940.patch
>
>
> We need support in Solr for the new TrieRange Lucene functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
