Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: <CAN4YXvcQqe1-+zva692YKEdyW01GqAfufcAe8SqM05zk6OXDQQ@mail.gmail.com>
References: <CAHTScUgGZXFLO0Kva5Fk7SftEtbh8MNeip4Ma3GLPjTeaonfyQ@mail.gmail.com>
 <CAHTScUhD0=Zc1m4FrHz7S5cA07q=Pb+3HxhmMppYcTUmMF4b7g@mail.gmail.com>
 <CAHTScUjsDudzYuuqLirWr+TQ4OkgsfOZ9ZrSEikc7kJaPLJs8Q@mail.gmail.com>
 <CAHTScUjYNjO6Ecx1osbJT4Asbo87QHtSYhC+gVHM+UdZ+xvwRg@mail.gmail.com>
 <CAHTScUh_w3eUUdde3xxX5jBDLRkdAsXi5Ed1geQSCzTiT6f5ww@mail.gmail.com>
 <CAHTScUjaa0aa4rYCpCBFCWRzZR5yCsk0d=PTQDpjYbXZcQ2YBA@mail.gmail.com>
 <CAHTScUgnRyJUHYsMam7Jxus3hexkV_PQ9bvLBxA84B3YO5XdoA@mail.gmail.com>
 <CAPsWd+PPFw2cyZuNpPhERU4VouGhEm5CcW07D1u1Ng-y6MW_Rw@mail.gmail.com>
 <CAHTScUiNkXKAyxgYR06NQqmiZuaAdxvDAGXZTL=RsCbfnCRzrg@mail.gmail.com> <CAN4YXvcQqe1-+zva692YKEdyW01GqAfufcAe8SqM05zk6OXDQQ@mail.gmail.com>
From: Michael McCandless <lucene@mikemccandless.com>
Date: Fri, 23 Dec 2016 06:21:19 -0500
Message-ID: <CAL8PwkZS0y4Sru9BNwJv3tZoKGEzMHrEyf4U4ngX48rupqq6Ng@mail.gmail.com>
Subject: Re: Sorting, Range Query, faceting - NumericDocValuesField Vs LongField
To: Lucene Users <java-user@lucene.apache.org>, Kumaran R <kums.134@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 23 Dec 2016 11:21:54 -0000

Note that Erick is giving you the Solr syntax below, but if you are
using Lucene directly, that obviously doesn't apply (though the same
general concepts do).

I would strongly recommend not using uninversion: it's an archaic and
costly option that Lucene only offered long ago because it didn't have
doc values, but that changed many years ago now.

Also the new dimensional points (IntPoint, LongPoint) give better
performance than the legacy postings based ("trie") numerics.

See https://www.elastic.co/blog/apache-lucene-numeric-filters for some
of the history here ...

Mike McCandless

http://blog.mikemccandless.com


On Thu, Dec 22, 2016 at 10:37 PM, Erick Erickson
<erickerickson@gmail.com> wrote:
> bq: Does this mean LongField/IntField just supports lexicographic
> order in sorting?
>
> no on several counts.
>
> No numeric type (long, int, float, double or trie values) support
> lexicographic sorting. That's the whole _point_ of having numeric
> types in the first place. Well, and efficient range queries in the
> Trie variants.
>
> docValues are an additional _attribute_ on the field so it's perfectly
> reasonable to have a long field that's both
> indexed=3D"true"  and docValues=3D"true". Or
> indexed=3D"true"  and docValues=3D"false". Or
> indexed=3D"false" and docValues=3D"true". Or
> indexed=3D"false" and docValues=3D"false"
>
> Do not think of them as separate field types.
>
> indexed=3D"true" is _required_ for searching. A field with
> indexed=3D"true" and docValues=3D"false" also supports faceting, grouping
> and sorting (numeric).
>
> A field with docValues=3D"true" just supports faceting, grouping and
> sorting without having to "uninvert" the field in the Java heap, the
> data is out in OS cache. See Uwe's excellent blog here:
> http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html
>
> Best,
> Erick
>
> On Thu, Dec 22, 2016 at 6:57 PM, Kumaran Ramasubramanian
> <kums.134@gmail.com> wrote:
>> Thank you Adrien.
>>
>> "NumericDocValuesField is the one that supports sorting."
>>
>> Does this mean LongField/IntField just supports lexicographic order in
>> sorting?
>>
>>
>> -
>> Kumaran R
>>
>>
>>
>> On Dec 22, 2016 11:28 PM, "Adrien Grand" <jpountz@gmail.com> wrote:
>>
>> Le jeu. 22 d=C3=A9c. 2016 =C3=A0 18:50, Kumaran Ramasubramanian <kums.13=
4@gmail.com>
>> a =C3=A9crit :
>>
>>> I want to provide sorting, range search and faceting in numeric fields.
>>>
>>> AFAIK, Purpose of different numeric field types are,
>>>
>>> NumericDocValuesField supports sorting and faceting
>>> LongField/IntField supports range query and sorting
>>>
>>
>> LongField/IntField only support querying, NumericDocValuesField is the o=
ne
>> that supports sorting.
>>
>> Also note that as of 6.0 LongField and IntField have been replaced with
>> LongPoint and IntPoint.
>>
>>
>>> 1. Should i duplicate one field in above mentioned types to achieve all
>> the
>>> three features in numeric?
>>>
>>
>> Yes. By the way it is perfectly fine to use the same field name for the
>> point field and the doc values field.
>>
>>
>>> 2. If i am ready to sacrifice faceting, is it advisable to use LongFiel=
d
>>> for sorting and range query?
>>>
>>
>> Like said above you need doc values for sorting.
>>
>>
>>> 3. During sorting, Will NumericDocValuesField( column stride storage)
>>> perform better than LongField(trie structure)? If so , should i duplica=
te
>>> field in both 1 and 2 cases?
>>>
>>
>> Same note here.
>>
>> Adrien
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>

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