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-8655) Add a default keyspace to CassandraSink
Date Wed, 23 May 2018 07:00:00 GMT

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

ASF GitHub Bot commented on FLINK-8655:

Github user zentol commented on the issue:

    That the example doesn't work isn't related to this PR so I'll merge it as is.
    But I'll take a look what the problem is, and either fix it or open a JIRA.

> Add a default keyspace to CassandraSink
> ---------------------------------------
>                 Key: FLINK-8655
>                 URL: https://issues.apache.org/jira/browse/FLINK-8655
>             Project: Flink
>          Issue Type: Improvement
>          Components: Cassandra Connector
>    Affects Versions: 1.4.0
>            Reporter: Christopher Hughes
>            Priority: Minor
>              Labels: features
>             Fix For: 1.6.0
> Currently, to use the CassandraPojoSink, it is necessary for a user to provide keyspace
information on the desired POJOs using datastax annotations.  This allows various POJOs to
be written to multiple keyspaces while sinking messages, but prevent runtime flexibility.
> For many developers, non-production environments may all share a single Cassandra instance
differentiated by keyspace names.  I propose adding a `defaultKeyspace(String keyspace)`
to the ClusterBuilder.  POJOs lacking a definitive keyspace would attempt to be loaded to
the provided default.

This message was sent by Atlassian JIRA

View raw message