[
https://issues.apache.org/jira/browse/LUCENE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783872#action_12783872
]
Mark Miller commented on LUCENE-2094:
-------------------------------------
bq. We are discussing only about one line, if we deprecate the explicit boolean
arg or not.
One line thats part of this patch. By committing, you remove incentive to deal
with the issue as the patch works in line with this being a bug. Now its in the
code, now everyone can go home and forget.
bq. because Robert and Simon want to go forward with other analyzer/unicode
work.
Whats the rush? They can do other work without this being in trunk today. Thats
not a valid reason for any commit in my mind.
bq. So this commit does not remove anything. And Version was introduced already
in 2.9.
I don't think it matters - where is the consensus to do this commit now after
discussion around it (one line or not) started? I don't see it.
> Prepare CharArraySet for Unicode 4.0
> ------------------------------------
>
> Key: LUCENE-2094
> URL: https://issues.apache.org/jira/browse/LUCENE-2094
> Project: Lucene - Java
> Issue Type: Bug
> Components: Analysis
> Affects Versions: 3.0
> Reporter: Simon Willnauer
> Assignee: Uwe Schindler
> Fix For: 3.1
>
> Attachments: LUCENE-2094.patch, LUCENE-2094.patch, LUCENE-2094.patch,
> LUCENE-2094.patch, LUCENE-2094.patch, LUCENE-2094.txt, LUCENE-2094.txt,
> LUCENE-2094.txt
>
>
> CharArraySet does lowercaseing if created with the correspondent flag. This
> causes that String / char[] with uncode 4 chars which are in the set can not
> be retrieved in "ignorecase" mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
