y-check-on-numeric-types-and-which-of-them-to-use-tp473893p784295.html
Sent from the Solr - User mailing list archive at Nabble.com.
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
to use a "sint" field is for backward compatibility
>> and/or to use sortMissingFirst/SortMissingLast, correct?
>
> I believe so.
>
> -Yonik
> http://www.lucidimagination.com
>
>
--
View this message in context:
http://old.nabble.com/Sanity-check-on-numeric-types-and-which-of-them-to-use-tp26651725p26655009.html
Sent from the Solr - User mailing list archive at Nabble.com.
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
Looking at the example version of schema.xml there seems to be some
confusion on which numeric field types are best used in different
situations. What confused me was that the type of "int" is now set to a
TrieIntField, but with a precisionStep of 0:
'
the "tint" type is set up as a TrieIntFiel
