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

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

Github user mcfongtw commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4696#discussion_r140620229
  
    --- Diff: docs/dev/connectors/cassandra.md ---
    @@ -78,76 +96,195 @@ Note that that enabling this feature will have an 
adverse impact on latency.
     
     <p style="border-radius: 5px; padding: 5px" class="bg-danger"><b>Note</b>: 
The write-ahead log functionality is currently experimental. In many cases it 
is sufficent to use the connector without enabling it. Please report problems 
to the development mailing list.</p>
     
    +### Checkpointing and Fault Tolerance
    +With checkpointing enabled, Cassandra Sink guarantees at-least-once 
delivery of action requests to C* instance.
     
    -#### Example
    +<p style="border-radius: 5px; padding: 5px" 
class="bg-danger"><b>Note</b>:However, current Cassandra Sink implementation 
does not flush the pending mutations  before the checkpoint was triggered. 
Thus, some in-flight mutations might not be replayed when the job recovered. 
</p>
    --- End diff --
    
    Good eye. Thanks


> Better documentation and examples on C* sink usage for Pojo and Tuples data 
> types
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-7632
>                 URL: https://issues.apache.org/jira/browse/FLINK-7632
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Cassandra Connector, Documentation
>            Reporter: Michael Fong
>            Assignee: Michael Fong
>
> Cassandra sink supports Pojo and Java Tuple data types. We should improve 
> documentation on its usage as well as some concrete / meaningful examples for 
> both cases. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to