lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: Should o.a.l.util.Constants declare all versions?
Date Mon, 23 May 2011 15:49:05 GMT
We also have Version.LUCENE_XX, which we declare for all versions that
were needed for back compat somewhere (I think)?  Can we somehow match
up SegmentInfo.getVersion to those constants?

Mike

http://blog.mikemccandless.com

On Mon, May 23, 2011 at 11:10 AM, Shai Erera <serera@gmail.com> wrote:
> Hi
>
> Today, that class declares only one field LUCENE_MAIN_VERSION, which is
> changed between releases. When 3.1 was released, it was set to "3.1" and now
> it is set to "3.2".
>
> I think that it will be good if we have a constants per version that can be
> found in a SegmentInfo.getVersion(), so that we can easily compare a certain
> SI.getVersion() w/ some release. We already have the following versions:
> "2.x" - for any pre-3.0 indexes
> "3.0"
> "3.1"
> "3.2" (in 3x, unreleased)
> "4.0" (in trunk, unreleased)
>
> This will be useful for LUCENE-2921 as well.
>
> Shai
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message