: From my understanding this could be also dangerous for queries that
: reduce the number of tokens.
: Imagine: Search Engine => SE (reduced to SE).
: This should have the same impact on the min should match as a stopword, no?
Not really ... assuming you mean *query* based synonyms, then a multiw
I've read in another thread
(http://lucene.472066.n3.nabble.com/Indexing-slower-in-trunk-td3059836.html#a3062991)
/Since Lucene 2.9, Lucene works on a per segment basis when searching. Since
Lucene 3.1 it can even parallelize on multiple segments. If you optimize
your index you only have one segm
Thanks so much, this helped a lot :)
- Original Message -
From: Uwe Schindler
To: java-user@lucene.apache.org; 'sol myr'
Cc:
Sent: Tuesday, October 4, 2011 12:14 PM
Subject: RE: [Lucene] Frequencies and positions - are they stored per field?
Hi,
Term Vectors are somehow duplicate in
Hello,
I'm using Lucene 3.4.0 and I would like to create a custom file with each
segment file Lucene creates (without modifying the source code).
I managed to create a custom indexing chain to create my file (e.g. _0.map,
_1.map ...) and it works!
I also created a custom IndexWriter to override