On Dec 22, 2004, at 11:25 PM, Kauler, Leto S wrote:
java.lang.RuntimeException: no terms in field Title_Sort - cannot
determine sort type
Title_Sort is a sort-specific field (Store=false, Index=true,
Tokenise=false). I do not have access to the actual Lucene-calling
code, but I do not believe
: The issue occurs if the first field it accesses parses as a numeric
: value and then successive fields are String's. If you are mixing and
: I am wondering why this exception might occur when the server/index is
: under load. I do realise there are many 'variables in the equation',
: so
:
On Thursday 23 December 2004 05:25, Kauler, Leto S wrote:
java.lang.RuntimeException: no terms in field Title_Sort - cannot
determine sort type
Is it a certain query that causes this? Does it really only happen under
load or does the same query also give this without load?
We could specify
Thanks for the replies! It would seem best for us to move to specifying
the sort type--good practice anyway and prevents possible field
problems. I plan to run the stress testing again today but turning off
the sorting (just using default SCORE) and see how that goes.
Seasons greetings to you
On Dec 23, 2004, at 6:15 PM, Kauler, Leto S wrote:
Erik Hatcher wrote:
*Everything* in Lucene is indexed as a string. But how a
date looks as
a string is a topic unto itself. I prefer to use MMDD as a date
formatted as a string (but when sorting, this could be treated as a
numeric).
Will
