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

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

Github user zentol commented on the pull request:

    https://github.com/apache/flink/pull/1660#issuecomment-189310673
  
    Overall this PR looks good now. I'll go through the documentation more in 
detail when i unify the docs for this PR and #1640 when merging.
    
    Furthermore, I'd like to make a slight change as to how the sink is 
created. Although there will be 2 separate sinks providing different guarantees 
in terms of data consistency, it would be nice if the sink creation would go 
through the same mechanism.
    
    @rmetzger drafted the following when i had a chat with him:
    ```
    CassandraSink sink = CassandraSink.addSink(input)
        .setHostname(..) //passing the hostname separately is intended for 
simple programs
        .setQuery(...)
        .setConsistencyLevel(...) //decides which sink is used
        .setClusterBuilder(new ClusterBuilder() { //optional, for maximum 
configurability
                @Override
                public Cluster createCluster(Cluster.Builder builder){
                        builder.addContactPoint(host).build();
                }
        .otherStuff()
        .build();
    ```
    CassandraSink would be a wrapper class, exposing common methods a user 
would expect from a sink.
    
    If you have no objections i would inject these changes while merging as 
well.


> Add a connector for streaming data into Cassandra
> -------------------------------------------------
>
>                 Key: FLINK-3311
>                 URL: https://issues.apache.org/jira/browse/FLINK-3311
>             Project: Flink
>          Issue Type: New Feature
>          Components: Streaming Connectors
>            Reporter: Robert Metzger
>            Assignee: Andrea Sella
>
> We had users in the past asking for a Flink+Cassandra integration.
> It seems that there is a well-developed java client for connecting into 
> Cassandra: https://github.com/datastax/java-driver (ASL 2.0)
> There are also tutorials out there on how to start a local cassandra instance 
> (for the tests): 
> http://prettyprint.me/prettyprint.me/2010/02/14/running-cassandra-as-an-embedded-service/index.html
> For the data types, I think we should support TupleX types, and map standard 
> java types to the respective cassandra types.
> In addition, it seems that there is a object mapper from datastax to store 
> POJOs in Cassandra (there are annotations for defining the primary key and 
> types)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to