[
https://issues.apache.org/jira/browse/FLINK-36828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17947873#comment-17947873
]
Lorenzo Nicora commented on FLINK-36828:
----------------------------------------
I have a working [example]
([https://github.com/aws-samples/amazon-managed-service-for-apache-flink-examples/blob/main/java/KinesisSourceDeaggregation/flink-app/src/main/java/com/amazonaws/services/msf/deaggregation/KinesisDeaggregatingDeserializationSchemaWrapper.java)]
using a wrapping `KinesisDeserializationSchema`
As adding de-aggregation support directly to the source seems to require
breaking the API (see FLINK-32097 and [GitHub Pull Request
#188|https://github.com/apache/flink-connector-aws/pull/188]) would not it be
simpler adding `KinesisDeaggregatingDeserializationSchemaWrapper` to the
connector and document it's usage?
> Implement example for customers to perform KPL Deaggregation
> ------------------------------------------------------------
>
> Key: FLINK-36828
> URL: https://issues.apache.org/jira/browse/FLINK-36828
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kinesis
> Affects Versions: aws-connector-5.0.0
> Reporter: Hong Liang Teoh
> Priority: Major
>
> We want to give an example to customers on how they can implement custom
> KinesisDeserializationSchema to perform KPL deaggregation
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
