Github user ramkrish86 commented on the issue:
https://github.com/apache/flink/pull/2332
With in a single row you need guarantee of order of execution? I agree
Append/Increment or non-idempotent in certain failure cases but there is a
Nonce generator for that. I should say I have not used that anyway to know the
exact pros and cons of that. RowMutations atleast it supports only Put/Delete
so in that angle you can be sure that for now we don't support
Append/Increments.
> we might need WriteAheadSink and figure out a way to roll back table to
the last checkpoint state
This will be tricky. Your hbase table rollback would mean that you may have
to issue Deletes here so that the previous mutations are hidden.
---
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.
---
