Yes it can read 3.x index files without extra configuaration. You cannot
enforce that, it is automatically.
Unfortunately, Lucene 4.10 has some problems, which will be fixed with a bugfix
release soon. Those bugs can lead to index corruption.
Maybe try 4.9.1 first.
Are you sure the 3.x index
Hi,
You should use a SpanQuery for this use-case. SpanQueries are a generalization
of PhraseQuery. You can include a FuzzyQuery using a MTQ wrapper query into a
span:
SpanNearQuery is the phrase, consisting of several
SpanMultiTermQueryWrapper(FuzzyQuery) nodes.
Be aware, that SpanQueries are
You should not have to configure anything.
The exception should not happen: can I have this index to debug the issue?
On Mon, Sep 22, 2014 at 11:07 PM, Patrick Mi
patrick...@touchpoint.co.nz wrote:
Hi there,
I understood that Lucene V4 could read 3.x index files by configuring
Lucene3xCodec
If you're looking for a parser, take a look at ComplexPhraseQueryParser or
LUCENE-5205.
From: Uwe Schindler [u...@thetaphi.de]
Sent: Tuesday, September 23, 2014 6:32 AM
To: java-user@lucene.apache.org
Subject: RE: How to use 'PhraseQuery' with Fuzzy?!
I opened an issue with a patch for this:
https://issues.apache.org/jira/browse/LUCENE-5975
Thanks for reporting it!
On Mon, Sep 22, 2014 at 11:07 PM, Patrick Mi
patrick...@touchpoint.co.nz wrote:
Hi there,
I understood that Lucene V4 could read 3.x index files by configuring
Lucene3xCodec
Hi Robert/Uwe,
Thanks very much for the quick response.
I have tried again with a different set of index(28k documents) generated
from V3 too and that worked.
But the one(30k documents) I tried indeed worked for the V3 but not V4.10.
Maybe something in that index could cause problem in V4 but
Hi Robert/Uwe,
I have tried v4.8 and v4.9 - not working either.
V4.7.0, V4.7.1, v4.7.2 are good.
Regards,
Patrick
-Original Message-
From: Patrick Mi [mailto:patrick...@touchpoint.co.nz]
Sent: Wednesday, 24 September 2014 12:24 p.m.
To: 'java-user@lucene.apache.org'
Subject: RE: How to
As reported in the issue, since 4.8 we do better checks when reading
this stuff in.
Unfortunately, 3.0-3.3 indexes had bugs in the way they encode the
deleted documents.
So for those indexes, we have to ignore the trailing garbage at the
end of the file.
On Tue, Sep 23, 2014 at 9:15 PM, Patrick