flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2055) Implement Streaming HBaseSink
Date Mon, 26 Sep 2016 06:19:21 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15522193#comment-15522193
] 

ASF GitHub Bot commented on FLINK-2055:
---------------------------------------

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?



> 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)

Mime
View raw message