Mailing-List: contact pylucene-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pylucene-dev@lucene.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.01.1110270454240.16687@yuzu.local>
References: <003601cc9479$d46c1af0$7d4450d0$@de>
	<alpine.OSX.2.01.1110270454240.16687@yuzu.local>
Date: Thu, 27 Oct 2011 09:40:22 -0400
Message-ID: 
 <CAL8PwkbyJD6zEFHLzyDEGQoY1QSeN-=piu-REqe+i6jsvMRMZQ@mail.gmail.com>
Subject: Re: SynonymAnalyzer(s) in PyLucene34
From: Michael McCandless <lucene@mikemccandless.com>
To: pylucene-dev@lucene.apache.org, Andi Vajda <vajda@apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 27, 2011 at 9:09 AM, Andi Vajda <vajda@apache.org> wrote:

> So, I downloaded the new version of the samples, hoping to find a new
> version of the wordnet index. But first, following instructions in README=
,
> running 'ant test' in the lia2e directory fails with:
> =A0 =A0Testcase: testWriteLock(lia.indexing.LockTest): =A0 =A0 Caused an =
ERROR
> =A0 =A0[junit] Unknown format version: -11
> during the CreateTestIndex step. Mike, what could that be ? (running Luce=
ne
> 3.4.0)

Hmmm, odd.  I couldn't reproduce this.  First I tried w/ the ZIP as
downloaded.  Then, I replaced the lib/lucene-core-3.0.2.jar with the
3.4.0 jar.  (Separately, I removed lucene-*-dev.jar: not sure why
those are in the zip file!).  "ant test" ran fine both times.

Did the LockTest fail or was it really during CreateTestIndex?  It
sounds like somehow something is opening a newer Lucene index than 3.x
(format -11 is likely referring to the segments file, which was added
for 3.1; so likely somehow it's using Lucene 3.0.x and trying to
access a 3.1 index).

LockTest uses an index in /tmp/index, so maybe that's where the
too-new index is being hit?

Mike McCandless

http://blog.mikemccandless.com