> > tests we get String but in distributed unit tests we get a
> > ByteArrayUtf8CharSequence instead.
> >
> > https://issues.apache.org/jira/browse/SOLR-13249
> >
> >
> >
> > -Original message-
> >> From:Andreas Hubold
> >> Sent: Friday 15
ira/browse/SOLR-13249
>
>
>
> -Original message-
>> From:Andreas Hubold
>> Sent: Friday 15th February 2019 10:10
>> To: solr-user@lucene.apache.org
>> Subject: Re: Solr 7.7 UpdateRequestProcessor broken
>>
>> Hi,
>>
>> thank you, Jan
y 15th February 2019 10:10
> To: solr-user@lucene.apache.org
> Subject: Re: Solr 7.7 UpdateRequestProcessor broken
>
> Hi,
>
> thank you, Jan.
>
> I've created https://issues.apache.org/jira/browse/SOLR-13255. Maybe you
> want to add your patch to that ticket. I did n
Hi,
thank you, Jan.
I've created https://issues.apache.org/jira/browse/SOLR-13255. Maybe you
want to add your patch to that ticket. I did not have time to test it yet.
So I guess, all SolrJ usages have to handle CharSequence now for string
fields? Well, this really sounds like a major breaki
Hi
This is a subtle change which is not detected by our langid unit tests, as I
think it only happens when document is trasferred with SolrJ and Javabin codec.
Was introduced in https://issues.apache.org/jira/browse/SOLR-12992
Please create a new JIRA issue for langid so we can try to fix it in
