On Mon, Nov 16, 2009 at 11:38 AM, Jeff Plater
wrote:
> Thanks - so if my sort field is a single term then I should be ok with
> using an analyzer (to lowercase it for example).
Correct - the key is that there is not more than one token per
document for the field being sorted on.
-Yonik
http://ww
09 11:19 AM
To: java-user@lucene.apache.org
Subject: Re: Sort fields shouldn't be tokenized
It's not universally true that a tokenized field cannot be used as a
sort field, but it is true that you will not get the desired sort
order except in special cases:
Lucene's indexes of cou
Thanks - so if my sort field is a single term then I should be ok with
using an analyzer (to lowercase it for example).
-Jeff
-Original Message-
From: J.J. Larrea [mailto:j...@panix.com]
Sent: Monday, November 16, 2009 11:19 AM
To: java-user@lucene.apache.org
Subject: Re: Sort fields
It's not universally true that a tokenized field cannot be used as a
sort field, but it is true that you will not get the desired sort
order except in special cases:
Lucene's indexes of course contain inverted tables which map Term ->
DocumentID, DocumentID, ...
But for sorting, once a set
