With the sequence number it should be trivial for mokuroku to find out about changes to the data records that were not passed through the index building function. That is, every time a particular index gets updated, store the sequence number for that index in the mrview--changes CF. Then when a query is made, check the changes sequence number and compare with the latest, if they differ, then get an iterator of the changes process the views just as with building an index for the first time.
This needs some more thought to work out the details, but that seems feasible in general, and avoids out of date indices.
With the sequence number it should be trivial for mokuroku to find out about changes to the data records that were not passed through the index building function. That is, every time a particular index gets updated, store the sequence number for that index in the
mrview--changesCF. Then when a query is made, check the changes sequence number and compare with the latest, if they differ, then get an iterator of the changes process the views just as with building an index for the first time.This needs some more thought to work out the details, but that seems feasible in general, and avoids out of date indices.