[
https://issues.apache.org/jira/browse/LUCENE-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336350#comment-14336350
]
Adrien Grand commented on LUCENE-6293:
--------------------------------------
I am not sure this is necessary. This bug cannot corrupt data, it can just
raise an ArrayIndexOutOfBoundsException if you happen to have a large array
which has a very specific pattern. So it is rather unlikely to happen in
practice, and even if it happens it would not corrupt data and would be easy to
identify as "TimSort" would be in the stack trace?
> TimSort bug
> -----------
>
> Key: LUCENE-6293
> URL: https://issues.apache.org/jira/browse/LUCENE-6293
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
>
> Robert pointed me to
> http://envisage-project.eu/proving-android-java-and-python-sorting-algorithm-is-broken-and-how-to-fix-it/
> yesterday which explains how most implementations of TimSort are broken. We
> should check our TimSorter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
