>
> The error is thrown by Lucene. Actually, multi valued fields are not very
> different from tokenized fields. Multiple values are indexed with their
> respective token positions differing by the positionIncrementGap value as
> specified in schema.
>
I truly understand that. But I guess, that is
On Tue, Aug 11, 2009 at 9:56 PM, Avlesh Singh wrote:
>
> However the RuntimeException that Solr throws has a misleading error
> message
> - "... but it's impossible to sort on tokenized fields". The field in this
> case is untokenized.
>
The error is thrown by Lucene. Actually, multi valued fiel
Ahhh, I should have seen this first. Your "contributororder" field is
multi-valued, you cannot sort on that field.
However the RuntimeException that Solr throws has a misleading error message
- "... but it's impossible to sort on tokenized fields". The field in this
case is untokenized.
Cheers
Av
Sure
The strange thing is that I could sort by another fields that is
defined using string, but not by another defined as some tokenized
field and after that copied as string.
I attach the schema.xml for the case is there another error and the
error log says the following
INFO: UnInverted mult
Can you please post the fieldType definition for the "string" field in your
schema.xml?
Cheers
Avlesh
On Tue, Aug 11, 2009 at 9:52 AM, Germán Biozzoli
wrote:
> Hello everybody
>
> I have the following (resumed) schema:
>
>
> multiValued="true"/>
>multiValued="true"/>
>multiValue
