[ 
https://issues.apache.org/jira/browse/LUCENE-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christoph Kaser updated LUCENE-6358:
------------------------------------
    Description: 
The static toLowerCase-method of UnescapedCharSequence does not account for 
locales in which the length of the result of String.toLowerCase is not the same 
as the length of the input string. This causes an 
ArrayIndexOutOfBoundsException, because wasEscaped and the chars array are not 
of the same length. 
(See attached test and patch)

  was:
The static toLowerCase-method of UnescapedCharSequence does nto account for 
locales in which the length of the result of String.toLowerCase is not the same 
as the length of the input string. This causes an 
ArrayIndexOutOfBoundsException, because wasEscaped and the chars array are not 
of the same length. 
(See attached test and patch)


> UnescapedCharSequence.toLowerCase throws ArrayIndexOutOfBoundsException for 
> certain input strings
> -------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-6358
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6358
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/queryparser
>    Affects Versions: 5.0
>            Reporter: Christoph Kaser
>            Priority: Minor
>         Attachments: LUCENE-6358-fix.patch, LUCENE-6358-test.patch
>
>
> The static toLowerCase-method of UnescapedCharSequence does not account for 
> locales in which the length of the result of String.toLowerCase is not the 
> same as the length of the input string. This causes an 
> ArrayIndexOutOfBoundsException, because wasEscaped and the chars array are 
> not of the same length. 
> (See attached test and patch)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to