It augments contrib/benchmark.
It's really more singularly focused on specific benchmarks for
indexing, searching, NRT performance, and you obviously have to know
Python to make use of it.
Whereas contrib/benchmark is far more powerful -- the algorithms
language give you lots of freedom on what t
Unfortunately, updateDocument replaces the *entire* previous document
with the new one.
The ability to update a single indexed field (either replace that
field entirely, or, change only certain token occurrences within it),
while leaving all other indexed fields in the document unaffected, has
bee
Thanks Ian, its as I feared!
I shall have to reindex (and upgrade!).
Cheers,
- Chris
-Original Message-
From: Ian Lea
To: java-user@lucene.apache.org
Sent: Fri, 8 Apr 2011 16:00
Subject: Re: Rewriting an index without losing 'hidden' data
Unfortunately you just can't do t
Unfortunately you just can't do this. Might be possible if all fields
were stored but evidently they are not in your index. For unstored
fields, the Document object will not contain the data that was passed
in when the doc was originally added.
I believe there might be a way of recreating some o
Is http://code.google.com/a/apache-extras.org/p/luceneutil/ designed
to replace or augment the contrib benchmark? For example it looks
like SearchPerfTest would be useful for executing queries over a
pre-built index. Though there's no indexing tool in the code tree?
-
OmniTI is pleased to announce that the CFP deadline for Surge 2011, the
Scalability and Performance Conference, (Baltimore: Sept 28-30, 2011) has
been extended to 23:59:59 EDT, April 17, 2011. The event focuses upon case
studies that demonstrate successes (and failures) in Web applications and
Inte
Hi,
I recently discovered that I need to add a single field to every document in an
existing (very large) index. Reindexing from scratch is not an option I want
to consider right now, so I wrote a utility to add the field by rewriting the
index - but this seemed to lose some of the fields (in
Yes, once you get the searcher you're free to access its underlying
IndexReader. Just don't close it!
And, be sure you call SearcherManager.release in a finally clause!
Else the reader will not be closed...
Mike
http://blog.mikemccandless.com
On Fri, Apr 8, 2011 at 6:54 AM, Piotr Pezik wrote:
If I am not mistaken Lucene Q&A mentions that you can update a document by
1. deleting it 2. adding the new one. Given that you have the ID this looks
straightforward.
Danica
On 8 April 2011 13:00, Patrick Diviacco wrote:
> Is there a way to update only 1 doc in the index rather than index the
Is there a way to update only 1 doc in the index rather than index the
entire collection everytime there is a change ?
Given a specific field (I use as ID) of my indexed doc, how can I select it
and update its other fields ?
thanks
Thanks for the tips.
Does the LIA SearcherManager provide/manage access to the IndexReader as well?
In other words, is it as easy as:
searcher.getIndexReader()
?
I need some of the the Reader methods in addition to the Searcher ones.
Piotr
On 8 Apr 2011, at 12:21, Michael McCandless wrote
Actually, you shouldn't need a separate ReadWriteLock.
SearcherManager (from LIA2's source code, freely downloadable from
http://www.manning.com/hatcher3, with Apache License 2.0) handles the
reference counting (so a reader is never closed while any search from
other threads are stil in flight), a
12 matches
Mail list logo
