On Thu, 6 Jan 2005, Erik Hatcher wrote:
>
> On Jan 6, 2005, at 10:41 AM, Joseph Ottinger wrote:
> > SHouldn't Lucene warn the user if they do something like this?
>
> When a user indexes a null? Or attempts to write to the index from two
> different IndexWriter instances?
>
> I believe you should
On Jan 6, 2005, at 10:41 AM, Joseph Ottinger wrote:
SHouldn't Lucene warn the user if they do something like this?
When a user indexes a null? Or attempts to write to the index from two
different IndexWriter instances?
I believe you should get an NPE if you try index a null field value?
No?
Well, I think I isolated the problem: stupid error on my part, I think. I
was adding an indexed field that had, um, a value of null. Correcting that
made the process go much more properly - although note that I haven't
scaled up to have multiple elements to index. Good milestone, though.
SHouldn't
Do you have two threads simultaneously either writing or deleting from
the index?
Erik
On Jan 6, 2005, at 9:27 AM, Joseph Ottinger wrote:
Sorry to reply to my own post, but I now have a greater understanding
of
PART of my problem - my SQLDirectory is not *quite* right, I think. So
I'
Sorry to reply to my own post, but I now have a greater understanding of
PART of my problem - my SQLDirectory is not *quite* right, I think. So I'm
rolling back to FSDirectory.
Now, I have a servlet that writes to the filesystem to simplify things (as
I'm not confident enough to debug the RDMS-bas
If this is a stupid question, I deeply apologize. I'm stumped.
I have a message-driven EJB using Lucene. In *every* case where the MDB is
trying to create an index, I'm getting "Lock obtain timed out."
It's in org.apache.lucene.store.Lock.obtain(Lock.java:58), which the user
list has referred to
