[
https://issues.apache.org/jira/browse/FLINK-25106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451559#comment-17451559
]
Varun Yeligar commented on FLINK-25106:
---------------------------------------
[~MartijnVisser] , In our use-case we want to receive all the messages
(including tombstone messages). We didn't go ahead with upsert-kafka connector
because it doesn't support specifying the
"[specific-offsets|https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/kafka/#scan-startup-specific-offsets]";
from which we want to start consuming the messages.
i.e. "kafka" connector supports specific-offsets but not tombstone messages
whereas "upsert-kafka" connectors supports tombstone messages but not the
specific-offsets.
In our use-case, we want to support both the cases (tombstone messages +
specific-offsets).
Please let me know if there is any alternative way to achieve both.
> Support tombstone messages in FLINK's "kafka" connector
> -------------------------------------------------------
>
> Key: FLINK-25106
> URL: https://issues.apache.org/jira/browse/FLINK-25106
> Project: Flink
> Issue Type: Improvement
> Components: API / Core
> Reporter: Varun Yeligar
> Priority: Minor
>
> Currently, FLINK's "kafka" connector ignores all the tombstone messages,
> whereas the "upsert-kafka" connector supports tombstone messages and sets the
> type of the row to RowKind.DELETE ([Code
> Link|https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-kafka/src/main/java/org/apache/flink/streaming/connectors/kafka/table/DynamicKafkaDeserializationSchema.java#L126]).
> I wanted to know if it is feasible to support tombstone messages in "kafka"
> connector by setting all the value fields to NULL and the RowKind to DELETE.
> I could also raise a PR with the respective changes if required.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
