[ https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130121#comment-14130121 ]
Tim Smith commented on LUCENE-5940: ----------------------------------- i understand the desire for changing the policy here. i wish i didn't have to care about backwards compat support, but its just the nature of things. people have large indexes that can take a significant amount of time to reindex (due to a slow source, or complex processing) the current proposal here would be problematic for any lucene users who do not release versions in lock step with lucene versions. Solr obviously would have limited issues here since a user could just upgrade to solr 4.99 (assuming 4.99 is the final 4.x version) and then solr 5.0 and no problems. however, if product X released with lucene 4.88 and the last minor version in 4.x line was 4.99, then the upgrade process to get to a lucene 5.0 index is now convoluted and will require creation of custom offline tools to provide an upgrade path. This backwards compatibility requirement is now just shifted from the lucene devs to the lucene users and can no longer be a seamless transition. the current policy does not have these issues since all that i would need to do is fire up the next version, do a forceMerge, and everything is up to date on latest codecs. (no offline processes required, search can continue to work during upgrade) > change index backwards compatibility policy. > -------------------------------------------- > > Key: LUCENE-5940 > URL: https://issues.apache.org/jira/browse/LUCENE-5940 > Project: Lucene - Core > Issue Type: Bug > Reporter: Robert Muir > > Currently, our index backwards compatibility is unmanageable. The length of > time in which we must support old indexes is simply too long. > The index back compat works like this: everyone wants it, but there are > frequently bugs, and when push comes to shove, its not a very sexy thing to > work on/fix, so its hard to get any help. > Currently our back compat "promise" is just a broken promise, because we > cannot actually guarantee it for these reasons. > I propose we scale back the length of time for which we must support old > indexes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org