[
https://issues.apache.org/jira/browse/FLINK-4498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323708#comment-17323708
]
Flink Jira Bot commented on FLINK-4498:
---------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Better Cassandra sink documentation
> -----------------------------------
>
> Key: FLINK-4498
> URL: https://issues.apache.org/jira/browse/FLINK-4498
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Cassandra, Documentation
> Affects Versions: 1.1.0
> Reporter: Elias Levy
> Assignee: Michael Fong
> Priority: Major
> Labels: stale-assigned
>
> The Cassandra sink documentation is somewhat muddled and could be improved.
> For instance, the fact that is only supports tuples and POJO's that use
> DataStax Mapper annotations is only mentioned in passing, and it is not clear
> that the reference to tuples only applies to Flink Java tuples and not Scala
> tuples.
> The documentation also does not mention that setQuery() is only necessary for
> tuple streams.
> The explanation of the write ahead log could use some cleaning up to clarify
> when it is appropriate to use, ideally with an example. Maybe this would be
> best as a blog post to expand on the type of non-deterministic streams this
> applies to.
> It would also be useful to mention that tuple elements will be mapped to
> Cassandra columns using the Datastax Java driver's default encoders, which
> are somewhat limited (e.g. to write to a blob column the type in the tuple
> must be a java.nio.ByteBuffer and not just a byte[]).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
