[
https://issues.apache.org/jira/browse/LUCENE-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857507#action_12857507
]
Robert Muir commented on LUCENE-2396:
-------------------------------------
bq. I can go along with this.
Cool!
bq. I still think it might be good to let the dust settle on the general
Version question before committing.
Sure... but we should still remember there's really no back compat for the
stuff changed in this patch :)
I'm also glad you mentioned the unicode issue, i mean if you are doing
non-English, some of the ideas in lucene's back compat with analyzers are
basically downright silly at the end of the day.
Besides the fact that upgrading your JVM can cause java itself to treat text
differently (which we currently cannot control), changes to the users operating
system [potentially completely outside of the scope of your application!] can
cause 'searches that worked before to not work anymore'.
For example, if your users upgrade and their new input method generates U+09CE
instead of U+09A4 U+09CD U+200D for Khanda-ta, the search won't match, even
though perhaps they typed the exact same key on their keyboard.
Unicode normalization does nothing in this case, and its your app's
responsibility to be aware of stuff like this (Not Lucene's analyzers!) and
deal with them.
At the end of the day, I think a lot of what lucene considers our own backwards
compatibility responsibility necessarily belongs in the app instead.
{noformat}
Versions of the Unicode Standard prior to Version 4.1 recommended that khanda
ta be represented
as the sequence <U+09A4 bengali letter ta, U+09CD bengali sign virama,
U+200D zero width joiner> in all circumstances. U+09CE bengali letter khanda ta
should instead be used explicitly in newly generated text, but users are
cautioned that
instances of the older representation may exist.
{noformat}
> remove version from contrib/analyzers.
> --------------------------------------
>
> Key: LUCENE-2396
> URL: https://issues.apache.org/jira/browse/LUCENE-2396
> Project: Lucene - Java
> Issue Type: Task
> Components: contrib/analyzers
> Affects Versions: 3.1
> Reporter: Robert Muir
> Assignee: Robert Muir
> Attachments: LUCENE-2396.patch
>
>
> Contrib/analyzers has no backwards-compatibility policy, so let's remove
> Version so the API is consumable.
> if you think we shouldn't do this, then instead explicitly state and vote on
> what the backwards compatibility policy for contrib/analyzers should be
> instead, or move it all to core.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
