Nathan Kurz wrote:
Except on NFS, KS doesn't have much in the way of lock contention
issues
because index files are never modified. But regardless of its
applicability
to KS, this "sneaky lock" trick is pretty nice:
...
We couldn't do that because we can't reach out across the system to
active
IndexReaders in other processes, but still: nice.
I realize this, but I'm wondering if a locking approach might be
preferable. Would the equivalent of row-level-locking allow you to
modify the index files in real time, instead of adding addenda and
tombstones? I'm not necessarily suggesting that the default index
format should do this, but that it might be worth considering whether
a proposed API would support such a real-time format.
What is this "sneaky lock" trick?
Mike
