> 3) The only reason to use a "sint" field is for backward compatibility
> and/or to use sortMissingFirst/SortMissingLast, correct?
>
I'm using sint so I can facet and sort facets numerically.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Sanity-check-on-numeric-types-
On Sat, Dec 5, 2009 at 7:02 AM, Marc Sturlese wrote:
>
> And what about:
> sortMissingLast="true"/>
> vs.
>
>
> Wich is the differenece between both? It's just bcdint always better?
> Thanks in advance
BCDInt was a very early attempt at a sortable int type that didnt go
through binary - it went
And what about:
vs.
Wich is the differenece between both? It's just bcdint always better?
Thanks in advance
Yonik Seeley-2 wrote:
>
> On Fri, Dec 4, 2009 at 7:38 PM, Jay Hill wrote:
>> 1) Is there any benefit to using the "int" type as a TrieIntField w/
>> precisionStep=0 over the "pint" ty
On Fri, Dec 4, 2009 at 7:38 PM, Jay Hill wrote:
> 1) Is there any benefit to using the "int" type as a TrieIntField w/
> precisionStep=0 over the "pint" type for simple ints that won't be sorted or
> range queried?
No. But given that people could throw in a random range query and
have it work co
