23 apr 2007 kl. 06.39 skrev Lucifer Hammer:
Thanks for that pointer! That link lead me to this link:
http://wiki.apache.org/lucene-java/BackwardsCompatibility - Which
makes it
sound like I can only expect backwards compatibility within the
current
major version.
Sorry, I read your post too fast. You are right, 3.0 may or may not
be able to read 2.0 indices.
When/if Lucene hits V3.0, it doesn't sound like there's a
commitment for it
to be able to read 2.X indexes. Right? How about Lucene 4.0, will
that be
able to read indexes in the 2.0 format? (Yes, I know there's a
migration
path, however, that's not our goal - we'd like to keep our current
2.0archives in
2.0 format, and know that we can read/search them from future
versions of
Lucene.
I'm curious, why is migrating the index not OK when it is OK to
upgrade the software? It doesn't really add up in my head.
One solution would be to load the 2.0-jar from a secondary
classloader. But that is probably not what you want though.
--
karl
Thanks
Lucifer
On 4/23/07, karl wettin <[EMAIL PROTECTED]> wrote:
23 apr 2007 kl. 06.10 skrev Lucifer Hammer:
> Should/can we expect that all future versions of Lucene will be
> able to read
> older indexes?
Yes.
<http://wiki.apache.org/lucene-java/
LuceneFAQ#head-5ad8d7368624fbe30cc1237d164c5820cf80e46b>
--
karl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
