lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Muir <rcm...@gmail.com>
Subject Re: LuceneTestCase.threadCleanup incorrectly reports left running threads
Date Mon, 27 Dec 2010 05:16:59 GMT
On Sun, Dec 26, 2010 at 5:17 AM, Uwe Schindler <uwe@thetaphi.de> wrote:
> About MD5: At least for Lucene 3.x we must stay with MD5, as changing the
> hash algorithm would change the lock file name, so an index locked with 3.0
> would have a different lock file than an index locked with 3.x (for external
> lock directory). This would lead to problems for users upgrading several
> servers writing to shared indexes during the upgrades. You cannot be sure
> that the same index is always locked when you have 2 different lucene
> versions. This is just a warning, maybe it’s not important, but its
> important.

Its not that important, as the hash algorithm uses getBytes() <--
default charset.

So, this functionality is already broken anyway, as it will hash the
same string to different hashes across different JVMs who happen to
have a different default charset.

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


Mime
View raw message