[
https://issues.apache.org/jira/browse/LUCENE-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778880#action_12778880
]
Mark Miller commented on LUCENE-2073:
-------------------------------------
{quote} If that's true, my inclination would be to add a note to the javadocs
for each
such class. In every case, it's theoretically possible to build alternative
implementations which are unaffected by upgrading the JVM. {quote}
I think thats a good idea, but I'd still like the top level warning as well - I
think it should be specific in explaining the problem, and not claim that it
exists for everything - Robert has already laid out a couple specific examples
we can mention. The problem with the javadoc approach only is that its very
easy to miss - I think its a good place to lay out the details for that
particular class - but it would still be great to have a visible top level
warning so that users know to be careful of this.
> 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]