[jira] [Updated] (FLINK-8655) Add a default keyspace to CassandraSink
[ https://issues.apache.org/jira/browse/FLINK-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chesnay Schepler updated FLINK-8655: Fix Version/s: (was: 1.5.0) 1.6.0 > 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 (v7.6.3#76005)
[jira] [Updated] (FLINK-8655) Add a default keyspace to CassandraSink
[ https://issues.apache.org/jira/browse/FLINK-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Hughes updated FLINK-8655: -- Component/s: Cassandra Connector > 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.5.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 (v7.6.3#76005)
[jira] [Updated] (FLINK-8655) Add a default keyspace to CassandraSink
[ https://issues.apache.org/jira/browse/FLINK-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Hughes updated FLINK-8655: -- Fix Version/s: (was: 1.4.1) 1.5.0 > Add a default keyspace to CassandraSink > --- > > Key: FLINK-8655 > URL: https://issues.apache.org/jira/browse/FLINK-8655 > Project: Flink > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Christopher Hughes >Priority: Minor > Labels: features > Fix For: 1.5.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 (v7.6.3#76005)
[jira] [Updated] (FLINK-8655) Add a default keyspace to CassandraSink
[ https://issues.apache.org/jira/browse/FLINK-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Hughes updated FLINK-8655: -- Description: 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. was: 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 that lack a keyspace would be piped to the default. > Add a default keyspace to CassandraSink > --- > > Key: FLINK-8655 > URL: https://issues.apache.org/jira/browse/FLINK-8655 > Project: Flink > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Christopher Hughes >Priority: Minor > Labels: features > Fix For: 1.4.1 > > > 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 (v7.6.3#76005)
