accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Parise, Jonathan" <>
Subject RE: Watching for Changes with Write Ahead Log?
Date Wed, 30 Sep 2015 13:20:02 GMT
In this particular case, I need to update some of my application state when changes made by
another system occur.

I would need to do a few things to accomplish my goal.

1)      Be notified or see that a table had changed

2)      Checked that against changes I know my system has made

3)      If my system is not the originator of the change, update internal state to reflect
the change.

Examples of state I may need to update include an ElasticSearch index and also an in memory

I’m going to read up on constraints again and see if I can use them for this purpose.



From: Adam Fuchs []
Sent: Tuesday, September 29, 2015 5:46 PM
Subject: Re: Watching for Changes with Write Ahead Log?


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.


On Tue, Sep 29, 2015 at 5:41 PM, Parise, Jonathan <<>>

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?


Jon Parise

View raw message