We're trying to convert an application from Lucene 3.6 to the current release.
We used to be able to pass the result of the static method below as the
FieldComparator in a SortField constructor. This code doesn't compile with the
latest release, but in converting it, we've been unable to get the
chindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Phil Herold [mailto:phil.her...@d-wise.com]
> Sent: Friday, January 17, 2014 2:37 AM
> To: java-user@lucene.apache.org
> Subject: FieldType.tokenized not the s
The last line in the test program below fails. I'm trying to store a keyword,
not tokenized, and get the same "type" of field back after query. But it
doesn't work, it comes back as "tokenized". Is this a known problem, or am I
missing something?
Thanks.
--
Phil
import org.apache.lucen
New information: it appears that the index size increasing (not always
doubling but going up significantly) occurs when I search the index while
building it. Calling indexWriter.optimize(1, true); when I'm done adding
documents sometimes reduces the index down to size, but not always.
Has anyon
I didn't have any errors or exceptions. Sorry to be dense, but what exactly
is the "infoStream output" you're asking about?
>This is not expected.
>
>Did the last IW exit "gracefully"? If so, it should delete the old
>segments after swapping in the optimized one.
>Can you post infoStre
I know that the size of a Lucene index can double while optimization is
underway, but it's supposed to eventually settle back down to the original
size, correct? We have a Lucene index consisting of 100K documents, that is
normally about 12GB in size. It is split across 10 sub-indexes which we
sear
Hi,
I'm getting incorrect search results when I use a MultiSearcher across
multiple indexes with a Boolean query, specifically, foo AND !bar (using
QueryParser). For example, with two indexes, I have a single document that
satisfies both "foo" and "bar", so it should be excluded from the search
