Steinert, Fabian wrote:
Hi,
you do not need to writer.close() the IndexWriter at all to make changes
visible.
When IndexWriter is constructed with autoCommit = true flag set,
calling writer.flush() will do.
Ok, but what about the write.lock? IndexWriter releases its write.lock only
I'm now looking at using payloads with SpanNearQuery but I don't see any
clear way of getting the payload(s) from the matching span terms. The term
positions for the payloads seem to be buried beneath SpanCells in the
NearSpansOrdered and NearSpansUnordered classes, which are not public. I'd
be
: I'm now looking at using payloads with SpanNearQuery but I don't see any
: clear way of getting the payload(s) from the matching span terms. The term
: positions for the payloads seem to be buried beneath SpanCells in the
Isn't Spans.start() and Spans.end() what you are looking for?
-Hoss
The lock file is only for Writers. The lock file ensures that even two
writers from two JVM's will not step on each other. Readers do not care
about what the writers are doing or whether there is a lock file...even
more so with the new generational files i believe.
- Mark
vcampa wrote:
