flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ramkrish86 <...@git.apache.org>
Subject [GitHub] flink issue #2332: [FLINK-2055] Implement Streaming HBaseSink
Date Mon, 26 Sep 2016 06:18:44 GMT
Github user ramkrish86 commented on the issue:

    https://github.com/apache/flink/pull/2332
  
    > This scheme does not provide exactly-once delivery guarantees, however at any given
point in time the table would be in a state as if the updates were only sent once. This is
the same guarantee that we provide for Cassandra.
    
    @zentol - so for Cassandra also it is atleast-once guarentee is what we provide? So even
if the mutations happens once again since the operations are idempotent we don't have any
issues with such duplicates? Am I getting it right here?



---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message