on index and move ('mv') newly built
index to its place. Notify using app that it should reopen its IndexReader.
This relies on UNIX file handling semantics. (Can't say a word about
Windows). Don't know if this applies at all to our situation, but it
works for us.
Danie
I would suggest you simply do not create unusable indexes. :-) Handle
catch/throw/finally correctly and it should not present any problems.
Assume one app builds the index, another uses it:
try: Build the index in a separate catalogue.
finally: remove ('rm') production index and move ('mv') newl
Agree. We run an index with about 2.5 million documents and around 30
fields. The indexing itself of 2 items should only take a few
seconds on a reasonably fast machine.
/D
Kevin L. Cobb wrote:
I think your bottleneck is most likely the DB hit. I assume by 2
products you mean 2 disti
Hi everybody,
We have been using Lucene for about one year now with great success.
Recently though the index has growed noticably and so has the number of
searches. I was wondering if anyone would like to comment on these
figures and say if it works for them?
Index size: ~2.5 GB, on disk
Number
