Thanks for your reply. I will have a look at this.
Peter Wolanin a écrit :
Seems like this might be approached using a Lucene payload? For
example where the original string is stored as the payload and
available in the returned facets for display purposes?
Payloads are byte arrays stored with Terms on Fields. See
https://issues.apache.org/jira/browse/LUCENE-755
Solr seems to have support for a few example payloads already like
NumericPayloadTokenFilter
Almost any way you approach this it seems like there are potentially
problems since you might have multiple combinations of case and accent
mapping to the same case-less accent-less value that you want to use
for sorting (and I assume for counting) your facets?
-Peter
On Fri, Jun 26, 2009 at 9:02 AM, Sébastien Lamy<lamys...@free.fr> wrote:
Shalin Shekhar Mangar a écrit :
On Fri, Jun 26, 2009 at 6:02 PM, Sébastien Lamy <lamys...@free.fr> wrote:
If I use a copyField to store into a string type, and facet on that, my
problem remains:
The facets are sorted case and accent sensitive. And I want an
*insensitive* sort.
If I use a copyField to store into a type with no accents and case (e.g
alphaOnlySort), then solr return me facet values with no accents and no
case. And I want the facet values returned by solr to *have accents and
case*.
Ah, of course you are right. There is no way to do this right now except
at
the client side.
Thank you for your response.
Would it be easy to modify Solr to behave like I want. Where should I start
to investigate?
