lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-1872) Improve javadocs for Numeric*
Date Sat, 29 Aug 2009 09:45:32 GMT


Michael McCandless commented on LUCENE-1872:

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

Ahh right.

I'm confused on why it's the "largest" value?  EG if I add 4, 17, 10 as a NumericField "x"
on my doc, when I then try to sort, wouldn't 10 "win" since it was added last to the document?

> Improve javadocs for Numeric*
> -----------------------------
>                 Key: LUCENE-1872
>                 URL:
>             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:
For additional commands, e-mail:

View raw message