[
https://issues.apache.org/jira/browse/FLINK-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511945#comment-15511945
]
ASF GitHub Bot commented on FLINK-2055:
---------------------------------------
Github user delding commented on the issue:
https://github.com/apache/flink/pull/2332
Hi @fhueske , in HBase writes to a single row have ACID guarantee. The
exactly once semantic can be implemented the way CassandraSink did, storing
input records in a state backend and flushing to HBase upon receiving a
checkpoint barrier. One thing that might be a concern is the order of execution
of these writes are not defined when making such a batch call. In other words,
a write of an earlier record could be observed later, but this could be also
true even sending each write immediately. So what do you think if implement
fault tolerance the same way as Cassandra Sink?
> Implement Streaming HBaseSink
> -----------------------------
>
> Key: FLINK-2055
> URL: https://issues.apache.org/jira/browse/FLINK-2055
> Project: Flink
> Issue Type: New Feature
> Components: Streaming, Streaming Connectors
> Affects Versions: 0.9
> Reporter: Robert Metzger
> Assignee: Erli Ding
>
> As per :
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Write-Stream-to-HBase-td1300.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
