: In our application we need to do this for all 20 fields. That means
: me have to create twenty redundant fields just for sorting.
: That's really an overhead in size and indexing-time.
I guess it just depends on the size of your index and how fast is "fast
enough" when indexing ... most people
Hi Chris,
sure, you can create an addional field for every field that should
support sorting.
In our application we need to do this for all 20 fields. That means
me have to create twenty redundant fields just for sorting.
That's really an overhead in size and indexing-time.
:: using the stored
: for years there is the discussion to make lucene able to sort on TOKENIZED
: fields.
really? .. i've only been on the list since 1.4.3 but i don't remember it
being much of a recurring topic.
: (e.g. if more then one term is available concatenate the tokens OR use the
: stored value for sortin
Hello,
for years there is the discussion to make lucene able to sort on TOKENIZED
fields.
(e.g. if more then one term is available concatenate the tokens OR use the
stored value for sorting).
Could some of the developer please make a statement if there are any
plans to implement this feature in
