Great, looks good! I think committer will do it but rebasing on master is
always a good thing.
The `CassandraPojoSink` is actually for streaming API. Unless we want to extend
`CassandraOutputFormatBase` with `CassandraPojoOutputFormat`, I think it is
better to use `CassandraTupleOutputFormat` for batch example in this PR, as it
was.
Sorry for confusion, can we roll it back to `CassandraTupleOutputFormat` for
batch example before merge (with `execute("write")` after `output`)?
`CassandraOutputFormatBase` can be extended with `CassandraPojoOutputFormat` in
other PR if needed.
[ Full content available at: https://github.com/apache/flink/pull/6735 ]
This message was relayed via gitbox.apache.org for [email protected]
