lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-940) TrieRange support
Date Tue, 30 Jun 2009 12:44:47 GMT

    [ https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725600#action_12725600
] 

Uwe Schindler commented on SOLR-940:
------------------------------------

bq. I think you are fixing it the wrong way. 

You misunderstood, I meant:
I fix it, that it is clear what it really does. I will not change RangeQuerys behaviour, I
will remove the whole internal Term handling in LUCENE-1713 and only use String field, lower,
upper. Then it is clear how it works. The current code has this strange behaviour (how it
handles Term instances)  because of the retrofitting of RangeQuery to MultiTermQuery.

> 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.


Mime
View raw message