[
https://issues.apache.org/jira/browse/LUCENE-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982407#action_12982407
]
Adriano Crestani commented on LUCENE-2867:
------------------------------------------
Hi Robert,
bq. 3.0.x and 2.9.x are bug fix release branches, but in my opinion some of the
issues surrounding using CharSequence in a HashSet/Map could be considered bugs.
API changes are not required to fix the CharSequence bug, so I'm not sure if I
should be adding and deprecating API methods on 2.9.x and 3.0.x.
> Change contrib QP API that uses CharSequence as string identifier
> -----------------------------------------------------------------
>
> Key: LUCENE-2867
> URL: https://issues.apache.org/jira/browse/LUCENE-2867
> Project: Lucene - Java
> Issue Type: Improvement
> Components: contrib/*
> Affects Versions: 3.0.3
> Reporter: Adriano Crestani
> Assignee: Adriano Crestani
> Priority: Minor
> Fix For: 3.0.4
>
> Attachments: lucene_2867_adriano_crestani_2011_01_13.patch
>
>
> There are some API methods on contrib queryparser that expects CharSequence
> as identifier. This is wrong, since it may lead to incorrect or mislead
> behavior, as shown on LUCENE-2855. To avoid this problem, these APIs will be
> changed and enforce the use of String instead of CharSequence on version 4.
> This patch already deprecate the old API methods and add new substitute
> methods that uses only String.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
