cshannon commented on PR #4242:
URL: https://github.com/apache/accumulo/pull/4242#issuecomment-1944302046
> This comment is not for a change on this PR, it just a discussion comment
about eventually adding the functionality in this PR to ZK store. To add
support for this in ZK store it seems like somehow we need the information
about expected status for an operation pushed up into AbstractFateStore and
then ieach mpl can enforce the expectation. For example somehow we put the fact
that delete() expects statuses {X,Y,Z} in AbstractFateStore and then both
stores check this requirement in their own way. Then the existing ITs that test
both stores can verify these status checks are working.
That would be interesting if we can enforce this with ZK. With Accumulo it
can be atomic with conditional mutations (obviously) but I would assume in ZK
we'd not be able to do it with one operation, we'd have to do a read to get the
status information and update so it wouldn't be Atomic. I guess we could
enforce this by having to synchronize/lock in the ZK implementation so that we
can read the status and prevent it from being changed until we are done
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
