Rather than your log file processor removing items from a log file,
have _it_ log the items that it _has_ re-indexed!
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-
Am 15.12.11 09:32, schrieb Tim Watts:
I'll try to refrain from chastising you for using a log as a work
queue... :-)
thank you :-)
but I suppose the "cleanest" way would be to log to a database and then
delete those rows once the files have been indexed.
I understand, but as you mention bel
I'll try to refrain from chastising you for using a log as a work
queue... :-)
but I suppose the "cleanest" way would be to log to a database and then
delete those rows once the files have been indexed.
Alternatively, if that adds too many moving parts and you want to stick
with text files, leave
Hi
As some of you might now Apache Lucene creates a "write.lock" when an
IndexWriter is updating the index,
hence it can happen that another IndexWriter (inside another thread)
won't be able to update the same index at the same time and based on a
specific timeout something might not get index