Regarding your message: RE: example on RegexQuery
I will be out of the office starting 27-Oct-2008 and will not return until
03-Nov-2008.
I will respond to your message when I return.
The information contained in this e-mail and any accompanying documents may
contain information that is c
u can get the 100 most relevant docs and
then sort only those, then you should look at FieldSortedHitQueue.
What you'd do is feed the top 100 documents into an instance
of FieldSortedHit queue then read traverse the queue.
If none of this applies, could you explain in a bit more detail?
Best
should look at FieldSortedHitQueue.
What you'd do is feed the top 100 documents into an instance
of FieldSortedHit queue then read traverse the queue.
If none of this applies, could you explain in a bit more detail?
Best
Erick
On Tue, Aug 5, 2008 at 4:35 PM, Neeraj Gupta
<[EMAIL PROTECTED]
Hi,
I need first 100 documents in a sorted order lets say sorted on the
document id and there are more then 50K documents in the index. My search
query is matching all those 50K documents. Is there any way to get only
first 100 documents that too in a sorted order of document id. I mean
Lucene
provided.
Cheers,
Neeraj
"Samuel LEMOINE" <[EMAIL PROTECTED]>
07/12/2007 09:38 PM
Please respond to
java-user@lucene.apache.org
To
java-user@lucene.apache.org
cc
[EMAIL PROTECTED]
Subject
Re: checking existing docs before indexing
Neeraj Gupta a écrit :
>
Hi,
You an use updateDocument() method of IndexWriter to update any existing
document.. It searches for a document matching the Term, if document
existes then delete that document. After that it adds the provided
document to the indexes in both the cases whether document exists or not.
Cheers,
e NativeFSLockFactory. I was hoping this would have
stopped these errors.
Patrick
On 03/07/07, Neeraj Gupta <[EMAIL PROTECTED]> wrote:
> Hi
>
> this is the case where index create by one server is updated by other
> server, results into index corruption. This exception occurin
Hi
this is the case where index create by one server is updated by other
server, results into index corruption. This exception occuring while
creating instance of Index writer because at the time of index writer
instance creation it checks if index exists or not, if you are not
creating a new
