lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonik Seeley <>
Subject Re: /trunk sortMissingLast="true" status?
Date Wed, 15 Sep 2010 01:53:13 GMT
On Tue, Sep 14, 2010 at 9:40 PM, Ryan McKinley <> wrote:
> Testing with r997128:
> I have a field defined as:
> <fieldType name="bytes"  class="solr.TrieLongField"
> sortMissingLast="true" precisionStep="0" omitNorms="true"
> positionIncrementGap="0"/>

SortMissingLast/SortMissingFirst is currently only supported with
fields that internally use a StringIndex (now DocTermsIndex) because
that's the only FieldCache representation that records what fields are
missing (via an ord of 0).

There's a note in the example schema.xml:

    <!-- The optional sortMissingLast and sortMissingFirst attributes are
         currently supported on types that are sorted internally as strings.
               This includes

That's actually the only reason the sint type fields are still around.
 If we could distinguish between 0 and missing, we could
deprecate/remove the s* fields and always use trie fields.

-Yonik  Lucene/Solr Conference, Boston Oct 7-8

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message