In the FAQ's it says that you have to do a manual incremental update:
How do I update a document or a set of documents that are already indexed?
There is no direct update procedure in Lucene. To update an index
incrementally you must first *delete* the documents that were updated, and
*then
The FAQ's have this index performance tip:
Use autoCommit=false when you open your IndexWriter
In Lucene 2.3 there are substantial optimizations for Documents that use
stored fields and term vectors, to save merging of these very large index
files. You should see the best gains by using
your organization... the
possibilities are endless. Which is why Lucene can't do that
for you.
Best
Erick
On Mon, Nov 10, 2008 at 2:22 PM, ChadDavis [EMAIL PROTECTED]
wrote:
In the FAQ's it says that you have to do a manual incremental update:
How do I update a document or a set
That's easy. Thanks.
On Mon, Nov 10, 2008 at 1:12 PM, Michael McCandless
[EMAIL PROTECTED] wrote:
Actually, all non-deprecated ctors of IndexWriter set autoCommit to false.
Ie, in 3.0 autoCommit false will become the only option.
Mike
ChadDavis wrote:
The FAQ's have this index
(it was
before my time!).
Mike
ChadDavis wrote:
I'm upgrading from a very old version of lucene to 2.4 I tried to
research
all the possible changes, this included reading the change file from the
2.4
version, which appears to reach back through all of the versions.
However,
I'm finding
will not necessarily be a float whose value is between 0 and 1.
Is this just stale documentation ?
On Sun, Nov 9, 2008 at 3:28 PM, ChadDavis [EMAIL PROTECTED]wrote:
The sample code uses a ScoreDoc array to hold the hits.
ScoreDoc[] hits = collector.topDocs().scoreDocs;
But the JavaDoc says
The sample code uses a ScoreDoc array to hold the hits.
ScoreDoc[] hits = collector.topDocs().scoreDocs;
But the JavaDoc says Expert: Returned by low-level search
implementations. Why would the tutorial sample code use an expert api?
Hey,
Is this list available somewhere that you can search the entire archives at
one time?
Thanks,
Chad
I just need a little confirmation of my understanding here.
If i say that a field is to be stored, the entire thing is written to the
index. It might also be indexed in a tokenized fasion if i also specify
that.
What are the advantages to storing a field then?
So you can search for that field?
I'm upgrading from a very old version of lucene to 2.4 I tried to research
all the possible changes, this included reading the change file from the 2.4
version, which appears to reach back through all of the versions. However,
I'm finding major API changes that aren't documented in that file.
10 matches
Mail list logo
