[jira] [Commented] (FLINK-9165) Improve CassandraSinkBase to send Collections

2018-04-12 Thread Christopher Hughes (JIRA)

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

Christopher Hughes commented on FLINK-9165:
---

Released a pull request for this issue 
(https://github.com/apache/flink/pull/5844)

> Improve CassandraSinkBase to send Collections
> -
>
> Key: FLINK-9165
> URL: https://issues.apache.org/jira/browse/FLINK-9165
> Project: Flink
>  Issue Type: Improvement
>  Components: Cassandra Connector
>Affects Versions: 1.4.2
>Reporter: Christopher Hughes
>Priority: Minor
>  Labels: easyfix, feature
>
> The CassandraSinkBase can currently only handle individual objects.  I 
> propose overloading the `send(IN value)` method to include 
> `send(Collection value)`. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (FLINK-9165) Improve CassandraSinkBase to send Collections

2018-04-12 Thread Christopher Hughes (JIRA)
Christopher Hughes created FLINK-9165:
-

 Summary: Improve CassandraSinkBase to send Collections
 Key: FLINK-9165
 URL: https://issues.apache.org/jira/browse/FLINK-9165
 Project: Flink
  Issue Type: Improvement
  Components: Cassandra Connector
Affects Versions: 1.4.2
Reporter: Christopher Hughes


The CassandraSinkBase can currently only handle individual objects.  I propose 
overloading the `send(IN value)` method to include `send(Collection 
value)`. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-8655) Add a default keyspace to CassandraSink

2018-02-21 Thread Christopher Hughes (JIRA)

 [ 
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

2018-02-14 Thread Christopher Hughes (JIRA)

 [ 
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

2018-02-14 Thread Christopher Hughes (JIRA)

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


[jira] [Created] (FLINK-8655) Add a default keyspace to CassandraSink

2018-02-14 Thread Christopher Hughes (JIRA)
Christopher Hughes created FLINK-8655:
-

 Summary: 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
 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 that lack a 
keyspace would be piped to the default. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)