script with the stateless script update processor.
> > > >
> > > Our workaround would be to not feed the multivalued field but only the
> > > String fields (which are also included in the multivalued field)
> > >
> > >
> > > Filing a Bug/Feature request
t only the
> > String fields (which are also included in the multivalued field)
> >
> >
> > Filing a Bug/Feature request and providing the patch will take some
> > time as I haven't setup a fully working trunk in my IDEA installation.
> > But I'm eager to do it
pansky
> >
> > -Original Message-
> > From: Müller, Stephan
> > Sent: Wednesday, November 27, 2013 5:02 AM
> > To: solr-user@lucene.apache.org
> > Subject: LanguageIdentifierUpdateProcessor uses only firstValue() on
> > multivalued fields
> >
> &g
-user@lucene.apache.org
Betreff: RE: LanguageIdentifierUpdateProcessor uses only firstValue() on
multivalued fields
> I suspect that it is an oversight for a use case that was not considered.
> I mean, it should probably either ignore or convert non text/string
> values.
Ok, I'll see tha
üller, Stephan
> Sent: Wednesday, November 27, 2013 5:02 AM
> To: solr-user@lucene.apache.org
> Subject: LanguageIdentifierUpdateProcessor uses only firstValue() on
> multivalued fields
>
> Hello,
>
> this is a repost. This message was originally posted on the 'gener
ssage-
From: Müller, Stephan
Sent: Wednesday, November 27, 2013 5:02 AM
To: solr-user@lucene.apache.org
Subject: LanguageIdentifierUpdateProcessor uses only firstValue() on
multivalued fields
Hello,
this is a repost. This message was originally posted on the 'general' list
but it was
Hello,
this is a repost. This message was originally posted on the 'general' list but
it was suggested, that the 'user' list might be a better place to ask.
Original Message
Hi,
we are passing a multivalued field to the LanguageIdentifierUpdateProcessor.
This multivalued field contai
