[
https://issues.apache.org/jira/browse/LUCENE-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778815#action_12778815
]
Uwe Schindler commented on LUCENE-2073:
---------------------------------------
How about adding a general note into some JRE_VERSION_MIGRATION.txt on each
release, also add this to the non-version specific site docs?
The first version that would contain it in the distribution would be 3.0, but
it should be noted on the site-docs, that this affects *all* versions.
Something like "whenever you change JRE major versions 1.4 -> 1.5 -> 1.6 -> 1.7
you may have to reindex, because the underlying VM's Unicode version could have
changed in a way, affecting your tokenizers."
> Document issues involved in building your index with one jdk version and then
> searching/updating with another
> -------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2073
> URL: https://issues.apache.org/jira/browse/LUCENE-2073
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Mark Miller
>
> I think this needs to go in something of a permenant spot - this isn't a one
> time release type issues - its going to present over multiple release.
> {quote}
> If there is nothing we can do here, then we just have to do the best we can -
> such as a prominent notice alerting that if you transition JVM's between
> building and searching the index and you are using or doing X, things will
> break.
> We should put this in a spot that is always pretty visible - perhaps even a
> new readme file titlted something like IndexBackwardCompatibility or
> something, to which we can add other tips and gotchyas as they come up. Or
> MaintainingIndicesAcrossVersions, or
> FancyWhateverGetsYourAttentionAboutUpgradingStuff. Or a permanent
> entry/sticky entry at the top of Changes.
> {quote}
--
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: [email protected]
For additional commands, e-mail: [email protected]
