[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725605#action_12725605
]
Uwe Schindler commented on SOLR-940:
------------------------------------
Yes, it now works with RangeQuery/Filter (as before), NumericRangeQuery/Filter
and FieldCacheRangeFilter.
I will fix the strange usage of Term instance when we deprecate the old
RangeQuery in favour of TermRangeQuery & Co. (LUCENE-1713).
The current check in RangeQuery ony prevents you to create a RangeQuery using
the Term instances (instead of field, string, string), where both are null
(because with both terms entirely null, no field name is available).
> 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.
