On Fri, May 2, 2008 at 8:17 AM, Geoffrey Young
<[EMAIL PROTECTED]> wrote:
> does this apply to facet fields as well? I noticed that that if I set
> facet.sort="true" the results are indeed sorted by count... until the counts
> are the same, after which they are in random order (instead of ascii a
Ok, thanks for the question as it would seem that I have found the answer.
Changing to a string field type fixes the problem. As we do not search over
the chapterTitle field this is no loss.
Thanks again for pointing me in the right direction
--
View this message in context:
http://www.nabble.
Erik Hatcher wrote:
>
> What field type is chapterTitle? I'm betting it is an analyzed
> field with multiple values (tokens/terms) per document. To
> successfully sort, you'll need to have a single value per document -
> using copyField can help with this to have both a searchable field
Erik Hatcher wrote:
What field type is chapterTitle? I'm betting it is an analyzed field
with multiple values (tokens/terms) per document. To successfully sort,
you'll need to have a single value per document - using copyField can
help with this to have both a searchable field and a sortab
What field type is chapterTitle? I'm betting it is an analyzed
field with multiple values (tokens/terms) per document. To
successfully sort, you'll need to have a single value per document -
using copyField can help with this to have both a searchable field
and a sortable version.
