You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jason Gerlowski (JIRA)" <ji...@apache.org> on 2019/03/01 18:00:00 UTC
[jira] [Commented] (SOLR-13255) LanguageIdentifierUpdateProcessor
broken for documents sent with SolrJ/javabin
[ https://issues.apache.org/jira/browse/SOLR-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781929#comment-16781929 ]
Jason Gerlowski commented on SOLR-13255:
----------------------------------------
Hey [~ahubold], have you had a chance to confirm whether 7.7.1 has fixed this issue for you? I trust Noble's fix, but there was a report on the mailing list this morning about a similar ClassCastException on Solr 7.7.1 so I figured it was worth checking in to see if you'd tried out the fix yet or had a chance to do so in the near future...
> LanguageIdentifierUpdateProcessor broken for documents sent with SolrJ/javabin
> ------------------------------------------------------------------------------
>
> Key: SOLR-13255
> URL: https://issues.apache.org/jira/browse/SOLR-13255
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - LangId
> Affects Versions: 7.7
> Reporter: Andreas Hubold
> Assignee: Noble Paul
> Priority: Blocker
> Fix For: 8.0, 7.7.1
>
> Attachments: SOLR-13255.patch, SOLR-13255.patch, SOLR-13255.patch
>
>
> 7.7 changed the object type of string field values that are passed to UpdateRequestProcessor implementations from java.lang.String to ByteArrayUtf8CharSequence. SOLR-12992 was mentioned on solr-user as cause.
> The LangDetectLanguageIdentifierUpdateProcessor still expects String values, does not work for CharSequences, and logs warnings instead. For example:
> {noformat}
> 2019-02-14 13:14:47.537 WARN (qtp802600647-19) [ x:studio] o.a.s.u.p.LangDetectLanguageIdentifierUpdateProcessor Field name_tokenized not a String value, not including in detection
> {noformat}
> I'm not sure, but there could be further places where the changed type for string values needs to be handled. (Our custom UpdateRequestProcessor are broken as well since 7.7 and it would be great to have a proper upgrade note as part of the release notes)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org