[
https://issues.apache.org/jira/browse/FLINK-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394012#comment-16394012
]
ASF GitHub Bot commented on FLINK-8655:
---------------------------------------
Github user Bekreth commented on the issue:
https://github.com/apache/flink/pull/5538
Previously, I was trying to leverage the current annotation parsers.
It would be possible to pass in a keyspace more directly into
AnotationParser in the shaded Datastax component, but I'm against this as it
requires maintaining a version Datastax that differs from the open source
version.
It could be possible to just replace the entire annotation with reflections
instead of just editing 1 property, but that still requires some futzing in
reflections that I think would be best to avoid.
Another option could be to extend the necessary Datastax classes within the
CassandraPojoSink to facilitate the alterations necessary to pass in keyspace
dynamically. I'm thinking this is the most favorable option.
> 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)
