Github user delding commented on the issue:
https://github.com/apache/flink/pull/2332
Hi @ramkrish86 , I'm thinking replace batch() with mutateRow() because it
provides atomic ordered mutations for a single row, but it only supports Put
and Delete which should be fine since only Put and Delete are idempotent, this
way we can implement Put and Delete without using WriteAheadSink (in case of
deterministic processing). What do you think?
Regarding Append and Delete, as HBase doesn't support distributed
transaction across multiple rows, we might need WriteAheadSink and figure out a
way to roll back table to the last checkpoint state. I'm thinking about this
right now.
So it might make sense to have two HBaseSinks, one for Put/Delet, the other
for Append/Delete and non-deterministic processing.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
