Hi Jack,
thank you for the hint.
Since I have already a solrj client to do the preprocessing, mapping to
sort fields isn't my problem. I will try to explain better in my reply
to Erick.
Uwe
(Sorry late reaction)
Am 30.08.2012 16:04, schrieb Jack Krupansky:
You can also use a Field
Am 31.08.2012 13:35, schrieb Erick Erickson:
... what would the correct behavior
be for sorting on a multivalued field
Hi Erick,
in generally you are right, the question of multivalued fields is which
value the reference is. But there are thousands of cases where this
question is implicit
If the Multiple-to-one mapping would be stable (e.g. independent of a
query), why not implement it as a custom update.chain processor with a copy
to a separate field? There is already a couple of implementations
under FieldValueMutatingUpdateProcessor (first, last, max, min).
Regards,
Alex.
Hi,
like I just wrote in my reply to the similar suggestion form Jack.
I'm not looking for a way to preprocess my data.
My question is, why do i need two redundant fields to sort a multivalued
field ('date_max' and 'date_min' for 'date')
For me it's just a waste of space, poisoning the
: My question is, why do i need two redundant fields to sort a multivalued field
: ('date_max' and 'date_min' for 'date')
: For me it's just a waste of space, poisoning the fieldcache.
how does two fields poion the fieldcache ? ... if there was a function
that could find the min or max value of
On Fri, 2012-09-07 at 06:55 +0200, Erick Erickson wrote:
I may prefer the first, and you may prefer the second. Neither is
necessarily more correct IMO, it depends on the problem
space. Choosing either one will be unpopular with anyone
who likes the other
Sorry, I did not make myself
And you've illustrated my viewpoint I think by saying
two obvious choices.
I may prefer the first, and you may prefer the second. Neither is
necessarily more correct IMO, it depends on the problem
space. Choosing either one will be unpopular with anyone
who likes the other
And I suspect that
On Fri, 2012-08-31 at 13:35 +0200, Erick Erickson wrote:
Imagine you have two entries, aardvark and emu in your
multiValued field. How should that document sort relative to
another doc with camel and zebra? Any heuristic
you apply will be wrong for someone else
I see two obvious choices
In addition to Jack's comment, what would the correct behavior
be for sorting on a multivalued field? The reason this is disallowed
is because there is no correct behavior in the general case.
Imagine you have two entries, aardvark and emu in your
multiValued field. How should that document sort
@lucene.apache.org
Subject: Sorting on mutivalued fields still impossible?
Hi,
just to be sure.
There is still no way to sort by multivalued fields?
...sort=max(datefield) desc
There is no smarter option, than creating additional singelevalued
fields just for sorting?
eg. datafield_max
Hi,
just to be sure.
There is still no way to sort by multivalued fields?
...sort=max(datefield) desc
There is no smarter option, than creating additional singelevalued
fields just for sorting?
eg. datafield_max and datefield_min
Uwe
11 matches
Mail list logo