i think the general assumption has always been that clucene updates will make old indeces invalid. There has also been several statements on the list re indeces in general being subject to change from engine updates (by addition of new fields etc). This was the core argument against making indices distributable and downloadable.
My best guess is that - if this is indeed so - then a frontend update with engine update should warn the user of indeces needing to be recreated - and probably also delete old indeces prior use.
Peter
-------- Original-Nachricht --------
> Datum: Fri, 16 Sep 2011 11:39:48 -0500
> Von: Greg Hellings <greg.hellings at gmail.com>
> An: "SWORD Developers\' Collaboration Forum" <sword-devel at crosswire.org>
> Betreff: [sword-devel] CLucene Compatibility
> While working on updating SWORD (and BibleTime) to handle CLucene
> 2.3.3.4 I have come across statements that clucene-core-0.9.21b is
> compatible with Lucene 1.9.1 and clucene-core-2.3.3.4 is compatible
> with Lucene 2.3. I asked Troy in IRC if this would mean invalidating
> any existing indexes. He believes that backwards compatibility is
> maintained by the 2.3 files but he wasn't sure. Does anyone know what
> the upgrade will entail for our users with existing indexes?
>> --Greg
>> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org>http://www.crosswire.org/mailman/listinfo/sword-devel> Instructions to unsubscribe/change your settings at above page
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de