-Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Friday, April 27, 2012 5:38 PM
> To: java-user@lucene.apache.org
> Subject: Re: Storing same field twice (analyzed+not-analyzed), sorting
>
> Hmmm, putting analyzed and unanalyzed values in
>
il 27, 2012 5:38 PM
To: java-user@lucene.apache.org
Subject: Re: Storing same field twice (analyzed+not-analyzed), sorting
Hmmm, putting analyzed and unanalyzed values in
the same field seems like it'd be difficult to get right. In
the Solr world, two separate fields are usually used.
Sortin
Hmmm, putting analyzed and unanalyzed values in
the same field seems like it'd be difficult to get right. In
the Solr world, two separate fields are usually used.
Sorting is right out, the results are unpredictable. What does
it mean to sort on a field with multiple tokens? For a doc
with "aardva
Hi,
I'm storing a field two times, one analyzed and other non-analyzed, in
order to be able to query for terms and for exact keyword:
// Analyzed version
d.add(new Field(key, value, Store.NO, Index.ANALYZED,
T