lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (LUCENE-1872) Improve javadocs for Numeric*
Date Sat, 29 Aug 2009 09:41:33 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749097#action_12749097
] 

Uwe Schindler edited comment on LUCENE-1872 at 8/29/09 2:40 AM:
----------------------------------------------------------------

This is correct (first part), you can add a field more than once and it really works (there
is a test about that: TestMultiValuedNumericRangeQuery). The results are the same like with
a normal range query (so the trie terms do not interfere between each other). See SOLR-1322

I think your sentence is a little bit complicated. It would hit all documents in the range,
where at least one of the values of a multi-valued doc is in the range.

About the second one: Sorting is not different from other numeric multi-value fields (in contrast
to StringIndex where only one value/doc is allowed). The univerter assigns a value to each
document. As it overrides values previously assigned to the document when iterating over all
terms in the field, the last term would be the one saved in the FieldCache. So you would sort
against the largest value per doc (because the smaller values are overridden by the larger
ones in the field cache).

      was (Author: thetaphi):
    This is correct (first part), you can add a field more than once and it really works (there
is a test about that). The results are the same like with a normal range query (so the trie
terms do not interfere between each other).

About the second one: Sorting is not different from other numeric multi-value fields (in contrast
to StringIndex where only one value/doc is allowed). The univerter assigns a value to each
document. As it overrides values previously assigned to the document when iterating over all
terms in the field, the last term would be the one saved in the FieldCache. So you would sort
against the largest value per doc (because the smaller values are overridden by the larger
ones in the field cache).
  
> Improve javadocs for Numeric*
> -----------------------------
>
>                 Key: LUCENE-1872
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1872
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.9
>
>
> I'm working on improving Numeric* javadocs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message