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-1322) range queries won't work for trie fields with precisionStep=0
Date Tue, 04 Aug 2009 14:23:14 GMT

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

Uwe Schindler commented on SOLR-1322:
-------------------------------------

bq. If trie fields are indexed in parts, NumericRangeQuery will produce invalid results for
multiValued fields... that's a limitation of the trie encoding (not easily fixable at all).


I do not really understand the problem with MultiValueFields. I had trie fields in my index
in the past that had multiple trie values and numeric range queries worked with it. What is
the problem? You should be able to add more than one value using separate Field instances
to the index.

A NumericRangeQuery on a MultiValued field should show results for all documents as soon as
*one* of the indexed values fall into the range. Correct me if I am wrong!

> range queries won't work for trie fields with precisionStep=0
> -------------------------------------------------------------
>
>                 Key: SOLR-1322
>                 URL: https://issues.apache.org/jira/browse/SOLR-1322
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.4
>            Reporter: Yonik Seeley
>            Assignee: Yonik Seeley
>             Fix For: 1.4
>
>
> range queries won't work for trie fields with precisionStep=0... a normal range query
should be used in this case.

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