> Better to fix it up so it's predictable and reliable instead, no?
Yes, you are absolutely right. Thats why I'm looking into this.
But how would i stuff, say always author_1, from a multi-valued field
into a single-valued (string or text) field?
Ok, another solution comes up to my mind.
Writing a processor for updateRequestProcessorChain, that might work.
Regards,
Bernd
Am 17.03.2011 16:27, schrieb Jonathan Rochkind:
Perhaps easiest thing for you right now, that you can do in any version of
Solr, is translate your data at indexing time so you don't have to
sort on a multi-valued field. Put the stuff in an additional field for sorting,
where at index time you only put the greatest or least value
(your choice) from a multi-valued set in, to have a single-valued field.
Your sorting on a multi-valued field before, while Solr let you, was almost
certainly resulting in unpredictable results in some cases, that you
just hadn't noticed. Better to fix it up so it's predictable and reliable
instead, no?
On 3/17/2011 11:14 AM, Bernd Fehling wrote:
Hi Yonik,
actually some applications "misused" sorting on a multiValued field,
like VuFind. And as a matter oft fact also FAST doesn't support this
because it doesn't make sense.
FAST distinguishes between multiValue and singleValue by just adding
the seperator-FieldAttribute to the field. So I moved this from FAST
index-profile to Solr DIH and placed the seperator there.
But now I'm looking for a solution for VuFind.
Easiest thing would be to have a kind of "casting", may be for copyField.
Regards,
Bernd
Am 17.03.2011 15:58, schrieb Yonik Seeley:
On Thu, Mar 17, 2011 at 10:34 AM, Bernd Fehling
<bernd.fehl...@uni-bielefeld.de> wrote:
Is there a way to have a kind of "casting" for copyField?
I have author names in multiValued string field and need a sorting on it,
but sort on field is only for multiValued=false.
I'm trying to get multiValued content from one field to a
non-multiValued text or string field for sorting.
And this, if possible, during loading with copyField.
Or any other solution?
I need this solution due to patch SOLR-2339, which is now more strict.
May be anyone else also.
Hmmm, you're the second person that's relied on that (sorting on a
multiValued field working).
Was SOLR-2339 a mistake?
-Yonik
http://lucidimagination.com
--
*************************************************************
Bernd Fehling Universitätsbibliothek Bielefeld
Dipl.-Inform. (FH) Universitätsstr. 25
Tel. +49 521 106-4060 Fax. +49 521 106-4052
bernd.fehl...@uni-bielefeld.de 33615 Bielefeld
BASE - Bielefeld Academic Search Engine - www.base-search.net
*************************************************************
