Doron Cohen wrote:
Antony Bowesman wrote:
Another use this may have is that mini-optimize operations could be
done at more
regular intervals to reduce the time for a full optimize. I could
then schedule
mini-optimise to run for a couple of minutes at more frequent intervals.
This seems to assume the proposed feature allows to continue an
interrupted merge at a later time, from where it was stopped. But
if I understood correctly then the proposed feature does not work
this way - so all the (uncommitted) work done until shutdown will
be "lost" - i.e. next merge() would start from scratch.
Yes, it does (wrongly) assume that. For some reason, I had thought the optimize
operation was a copy+pack operation, but of course, it's not, so I can see why
this incremental approach is not possible (or at least non trivial).
Still, the shutdown function would be useful on its own.
Antony
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
