Jon, You might think about putting a constraint on your table. I think the API for constraints is flexible enough for your purpose, but I'm not exactly sure how you would want to manage the results / side effects of your observations.
Adam On Tue, Sep 29, 2015 at 5:41 PM, Parise, Jonathan <jonathan.par...@gd-ms.com > wrote: > Hi, > > > > I’m working on a system where generally changes to Accumulo will come > through that system. However, in some cases, another system may change data > without my system being aware of it. > > > > What I would like to do is somehow listen for changes to the tables my > system cares about. I know there is a write ahead log that I could > potentially listen to for changes, but I don’t know how to use it. I looked > around for some documentation about it, and I don’t see much. I get the > impression that it isn’t really intended for this type of use case. > > > > Does anyone have any suggestions on how to watch a table for changes and > then determine if those changes were made by a different system. > > > > Is there some documentation about how to use the write ahead log? > > > > > > Thanks, > > > > Jon Parise >