lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DM Smith (JIRA)" <>
Subject [jira] Commented: (LUCENE-2396) remove version from contrib/analyzers.
Date Thu, 15 Apr 2010 17:41:50 GMT


DM Smith commented on LUCENE-2396:

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:
>             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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message