Github user ctamisier commented on the issue:
https://github.com/apache/flink/pull/5964
@zentol, @StephanEwen, @Bekreth
> We would have to pass the keyspace via the constructor as the
Configuration approach doesn't work for streaming.
I'm not sure to understand, the new unit test
(`testCassandraPojoNoAnnotatedKeyspaceAtLeastOnceSink`) is in the streaming
package (`org.apache.flink.streaming.connectors.cassandra`) and it seems to
work. Do I miss something about the general flink setup ?
> Generally speaking it isn't a problem to set the keyspace when creating
the connection. But I would like to know what happens if a POJO comes along
that explicitly sets the keyspace; is it ignored, respected or will it cause an
exception?
It takes the keyspace from the `@Table`. see `AnnotationParser.parseEntity`
method for `EntityMapper<T>` creation using `ksName`
It seems the default behavior of cassandra, I'm not sure we can do
something here..
---
