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. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Mon, Jan 7, 2013 at 8:19 AM, Uwe Reh <r...@hebis.uni-frankfurt.de> wrote: > 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 answered. See my example "...&sort=max(datefield) > desc&...." It is obvious, that the newest date should win. I see no reason > why simple filters like max can't handle multivalued fields. > > Now four month's later i still wounder, why there is no pluginable > function to map multivalued fields into a single value. > eg. "...&sort=sqrt(**mapMultipleToOne(FQN, fieldname)) asc&..." > > Uwe > (Sorry late reaction) > > >
