[
https://issues.apache.org/jira/browse/LUCENE-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857427#action_12857427
]
DM Smith commented on LUCENE-2396:
----------------------------------
Robert,
I think this is a red-herring. There has been an implicit bw compat policy,
with all the effort to maintain bw compat in the analyzers. With the
re-shuffling of contrib this has been made a bit murky and does need to be
re-addressed.
How is this any different than the discussion to eliminate Version altogether?
I think that should be resolved first and this follow the lead of that.
How can one have a useful index across releases without a stable token stream?
From the thread it is clear that few understand the impact of an analyzer on
the usefulness of an index.
If this succeeds there is little reason to maintain Version at all.
-- DM
> 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
