: If your concern is performance, faceting integers versus faceting strings, I
: believe Lucene makes the differences negligible. Given that choice I'd go
>From a speed standpoint, i believe the differnece is negligable, but from
a memory standpoint the datastructures for dealing with an integer
miter. Then parse it on display. But you can use the id if you need to
hit a database or some other external source. If you don't ever need to
reference the ID, I wouldn't even put it in the index.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Facet-Fields-ID-v
/search-lucene.com/
>>
>>
>>
>> ----- Original Message ----
>>> From: Frank A
>>> To: solr-user@lucene.apache.org
>>> Sent: Mon, August 9, 2010 5:19:57 PM
>>> Subject: Facet Fields - ID vs. Display Value
>>>
>>> Is there a general best practice on whether facet fields should be on
>>> "IDs" or "Display values"?
>>>
>>> -Frank
>>>
>>
>
--
Sent from my mobile device
lr-user@lucene.apache.org
>> Sent: Mon, August 9, 2010 5:19:57 PM
>> Subject: Facet Fields - ID vs. Display Value
>>
>> Is there a general best practice on whether facet fields should be on
>> "IDs" or "Display values"?
>>
>> -Frank
>>
>
g
> it
> was nice and clean.
>
> Otis
>
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
>
>
>
> - Original Message
>> From: Frank A
>> To: solr-user@lucene.apache.org
Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
> From: Frank A
> To: solr-user@lucene.apache.org
> Sent: Mon, August 9, 2010 5:19:57 PM
> Subject: Facet Fields - ID vs. Display Value
>
> Is there a general best practice on whether fa
Is there a general best practice on whether facet fields should be on
"IDs" or "Display values"?
-Frank
