I wonder if it would shed any light on the issue if you separated the two?
In other words, what would happen if you mocked up your MySQL connection and
just generated "responses" for Lucene to index without having the database
drivers even loaded?
Also, you could write the data from MySQL out to
Rahil wrote:
No I have around 50GB free on my extrenal disk in which Im creating the
indexes. So hopefully that shouldnt be the problem.
How is the external disk mounted? Samba from unix? NTFS? I wonder if
there isn't something strange going on here.
Have you tried building the index on a
Hi Paul
[EMAIL PROTECTED] wrote:
I can only think that the problem you're having is peculiar to your setup
or the way in which you are using Lucene. A wild guess - are you reaching
quota limits on your filesystem or something like this?
No I have around 50GB free on my extrenal disk in which
Another wild guess - it seems to be throwing the exception when merging
segments. Are you sure you've got write access to the directory that the
lock file is being created in. Lucene In Action has some details about
index locking and how you can change the location of the lock file - I'm
not s
I can only think that the problem you're having is peculiar to your setup
or the way in which you are using Lucene. A wild guess - are you reaching
quota limits on your filesystem or something like this?
Regards
Paul I..
Hi Dan
Dan Armbrust wrote:
The MySQL drivers are horrible at dealing with large result sets -
that article gives you the workaround to tell it to bring the results
back as they are needed (like it should in the first place) but I have
found that it isn't reliable - it tends to drop out at
