I know this has been covered a number of time before but I am still confused.
I am using all the default values for IndexWriter when writing my index.
I loop over all my documents 1000 at a time. For each 1000 I open an index
writer, write each document, optimize the index, then close the index
I am trying to figure out the best way to add to a lucene index across a
clustered app server. I cannot grab an IndexWriter for each node in the
cluster, because I would run into lock file problems. I am not sure if I can
share one IndexWriter across the cluster because what happens when two o
I am having a problem where I am getting lock timeouts when trying to write to
my index file. It would be nice if I could turn on logging to see which
server/application has the lock and when. Is there a way to see the lock
information without changing code?
Thanks,
Billy
___
mplements some sort of
fairness. If you do that please consider donating it back!
Mike
On Sat, May 16, 2009 at 10:44 AM, Newman, Billy wrote:
> At this point it would not be feasible to share the writer across the
> application and the build index process. And I shouldn't have to
ame index (the write lock enforces this).
Mike
On Fri, May 15, 2009 at 4:18 PM, Newman, Billy wrote:
> I am trying to build my indices file while still allowing my application to
> add new information and I my application cannot obtain the lock.
>
> Here is a little pseudo code o
I am trying to build my indices file while still allowing my application to add
new information and I my application cannot obtain the lock.
Here is a little pseudo code on what I am trying to do:
Build Indicies:
1. For each element (i.e. I have n elements I want to add to the index)
2.
I know that this is not really a lucene problem but looking around I have not
been able to find much about it.
I recently ran into a problem where I cannot obtain a lock due to a problem
with native file system locks. The strange thing is that this was working a
few days ago and I have just st
update by if that's a better solution.
>
> Best
> Erick
>
> On Mon, Apr 20, 2009 at 11:40 AM, Newman, Billy >wrote:
>
> > What if you're unique id is a composite of two field when you create the
> > document?
> >
> > I.E.
> > doc.add(new F
itive) that if you update a document where the
term doesn't
have any matches, you'll get a simple insert, but I won't guarantee it.
HTH
Erick
On Fri, Apr 17, 2009 at 9:28 PM, Newman, Billy wrote:
> Ok I am still confused.
>
> Looking at the examples to index
So I have recently switched to using NativeFSLockFactory so that when my jboss
instance is shutdown or comes down abnormally it does not leave lock files
around. My problem is that it is not working.
I have put in debug to be sure that I am really using NativeFSLockFactory. I
have tested this
r update
statement.
Think of the Term as a unique key for the document that *you've*
deliberately put there.
I'm pretty sure (but not positive) that if you update a document where the
term doesn't
have any matches, you'll get a simple insert, but I won't guarantee it.
HTH
E
nse? Am I going about this wrong?
Billy
From: Tim Williams [william...@gmail.com]
Sent: Friday, April 17, 2009 6:05 PM
To: java-user@lucene.apache.org
Subject: Re: IndexWriter update method
On Fri, Apr 17, 2009 at 7:27 PM, Newman, Billy wrote:
> I am looking for info on how to
I am looking for info on how to use the IndexWriter.update method. A short
example of how to add a document and then later update would be very helpful.
I get lost because I can add a document with just the document, but I need a
document and a Term. I am not really sure what a Term is since
13 matches
Mail list logo
