[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725568#action_12725568
]
Uwe Schindler edited comment on SOLR-940 at 6/30/09 4:30 AM:
-------------------------------------------------------------
Oh, this was intended.
the reason was, that all other range filters in lucene core do not allow this.
In general one should use a MatchAllDocsQuery in this case, as it is more
performant.
I could enable it again, but I have to think about the other range queries and
filters then.
How do you handle that with other range queries?
was (Author: thetaphi):
Oh, this was intended.
the reason was, that all other range filters in lucene core do not allow this.
In general one should use a MatchAllDocsQuery in this case, as it is more
performant.
I could enable it again, but I have to think about the other range queries and
filters then.
> 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.
