[
https://issues.apache.org/jira/browse/FLINK-20060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20060:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add a Collector to KinsesisDeserializationSchema
> ------------------------------------------------
>
> Key: FLINK-20060
> URL: https://issues.apache.org/jira/browse/FLINK-20060
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / Kinesis
> Reporter: Timo Walther
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> We did not add support for a collector in the KinesisDeserializationSchema.
> The problem with that connector lays in the threading model, where there is a
> pool of threads that read and deserialize records and then they handover the
> deserialized messages through a queue to the main thread. The problem is that
> we would need to create many temporary collections to put the deserialized
> records into the handover queue, which potentially would significantly affect
> performance, especially in the usual case of deserializing a single record
> from a single message.
> This means that we can currently not support the Debezium format for in the
> SQL connector if the Debezium record needs to emit 2 rows (UPDATE_BEFORE and
> UPDATE_AFTER).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
