OK I dug down on this one... it's actually a bug in IndexWriter, when
used in near real-time mode *and* when CFS is enabled. In that case,
internally IndexWriter holds open the wrong SegmentReader, thus tying
up more disk space than it should.
Functionally, the bug is harmless -- it's just tying
OK I opened https://issues.apache.org/jira/browse/LUCENE-2097 to track this.
Thanks v.sevel!
Mike
On Sun, Nov 29, 2009 at 5:57 AM, Michael McCandless
wrote:
> OK I dug down on this one... it's actually a bug in IndexWriter, when
> used in near real-time mode *and* when CFS is enabled. In that
Hi,
How to replace Collectors in Lucene-java in a
PyLucene script (PyLucene-3)
Many thanks for a hint,
Helmut.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
-
To un
Probably you should re-ask this on pylucene-...@l.a.o?
Mike
On Sun, Nov 29, 2009 at 7:25 AM, Helmut Jarausch
wrote:
> Hi,
>
> How to replace Collectors in Lucene-java in a
> PyLucene script (PyLucene-3)
>
> Many thanks for a hint,
> Helmut.
>
> --
> Helmut Jarausch
>
> Lehrstuhl fuer Numerische
See below
On Sat, Nov 28, 2009 at 4:39 PM, Karl Heinz Marbaise wrote:
> Hi Ian,
>
> many thanks for the hints...based on your and Ericks hints i have taken a
> deeper look into that...and the StandardAnalyzer which I'm using will
> removed informations like "." and "-" from my queries
> (+filenam
Hi all.
I've been playing a lot with the new query parser framework, primarily
as a means of converting a query structure back into a string. I was
hoping that I would be able to use it for the parsing direction as
well a bit later, to simply our customisations on the older query
parser, and that
Hello all,
I am having an index build using v2.4.1. I upgraded to 2,9.1. The index was
searchable. I added couple of documents and i found that the
PerFieldAnalyzerWrapper is not working as expected.
PerFieldAnalyzerWrapper analyzer = new PerFieldAnalyzerWrapper(getAnalyser());
analyzer.addAna
One small correction...
My default Analyzer is snowball analyzer and it is being used for all fields
(not KeywordAnalyzer) even though few fields should use different analyzer.
PerFieldAnalyzerWrapper is not considering the analyzer set for different
fields.
This is consistently reproducing
I can see no error,
Are you sure, that you are really using the PerFieldAnalyzerWrapper for both
indexing and searching? Field names are case sensitive! How does your index
look like with Luke?
Can you send us the code to reproduce this? E.g. some small 2.4.1 index
attached as zip and code that a
