[ 
https://issues.apache.org/jira/browse/LUCENE-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365075#comment-16365075
 ] 

Robert Muir commented on LUCENE-8175:
-------------------------------------

Since it will easily trip with threads on CJK/Thai and other common scripts, it 
would be good to address it before the next release.

I think we should first give ICU a chance. But if we want to release before 
they have released a fix, it would be best to just revert LUCENE-8122, 
LUCENE-8125, and Uwe's regenerate commit: 
https://github.com/apache/lucene-solr/commit/b3677c1a091209409590de3ec6bafde089323598#diff-1a83715f3cabfb71b96f435072789417
 in the 7.x branch? We could always backport them for a future 7.x release in 
such a case.

> ICUTokenizer might return corrupt tokens due to concurrency bug in ICU4J
> ------------------------------------------------------------------------
>
>                 Key: LUCENE-8175
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8175
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Adrien Grand
>            Priority: Critical
>
> I was digging some test failures with {{testRandomHugeStrings}} that occurred 
> since the upgrade to ICU4J 60.2 which happen to boil down to this bug: 
> http://bugs.icu-project.org/trac/ticket/13512 which is fixed but not released 
> yet.
> In short an int[] is shared across several threads while it shouldn't. As a 
> consequence, ICUTokenizer may sometimes return corrupt tokens. I pinged on 
> the issue to know when a release fixing this bug is expected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to