[
https://issues.apache.org/jira/browse/FLINK-26539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513383#comment-17513383
]
Martijn Visser commented on FLINK-26539:
----------------------------------------
[~ZhenqiuHuang] I can understand the need to not unintentionally write a null
in some user situations. But is that the case in all situations? I'm not sure
about that. So, is this a problem that should be solved for every Flink user
that's using Flink's Cassandra connector? Or should it be part of the user's
logic?
I think that only the user can decide if it's necessary to write a null or not.
Perhaps it makes sense to use Flink's Cassandra connector and add slightly
modify it, perhaps using the extensions available with FLIP-191
https://cwiki.apache.org/confluence/display/FLINK/FLIP-191%3A+Extend+unified+Sink+interface+to+support+small+file+compaction
Let me know what you think
> Support dynamic partial features update in Cassandra connector
> --------------------------------------------------------------
>
> Key: FLINK-26539
> URL: https://issues.apache.org/jira/browse/FLINK-26539
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / Cassandra
> Reporter: Zhenqiu Huang
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
