[
https://issues.apache.org/jira/browse/LUCENE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035361#comment-13035361
]
Uwe Schindler commented on LUCENE-3014:
---------------------------------------
It's fine, commit it!
We may look for usage of the version field in SegmentInfos, and use this
comparator there (especially e.g. my new one for upgrades or the standard
IndexTooOldException stuff).
But I think that should be a new issue.
> comparator API for segment versions
> -----------------------------------
>
> Key: LUCENE-3014
> URL: https://issues.apache.org/jira/browse/LUCENE-3014
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Robert Muir
> Assignee: Uwe Schindler
> Priority: Critical
> Fix For: 3.2
>
> Attachments: LUCENE-3014.patch
>
>
> See LUCENE-3012 for an example.
> Things get ugly if you want to use SegmentInfo.getVersion()
> For example, what if we committed my patch, release 3.2, but later released
> 3.1.1 (will "3.1.1" this be whats written and returned by this function?)
> Then suddenly we broke the index format because we are using Strings here
> without a reasonable comparator API.
> In this case one should be able to compute if the version is < 3.2 safely.
> If we don't do this, and we rely upon this version information internally in
> lucene, I think we are going to break something.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
