[
https://issues.apache.org/jira/browse/FLINK-36671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hong Liang Teoh updated FLINK-36671:
------------------------------------
Fix Version/s: aws-connector-5.1.0
> Kinesis Table API for new KDS source does not support metadata.
> ---------------------------------------------------------------
>
> Key: FLINK-36671
> URL: https://issues.apache.org/jira/browse/FLINK-36671
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kinesis
> Affects Versions: aws-connector-5.0.0
> Reporter: Hong Liang Teoh
> Priority: Major
> Fix For: aws-connector-5.1.0
>
>
> h2. What
> The old Kinesis Table API source `kinesis-legacy` supports defining virtual
> columns using table metadata.
> For example:
>
> {code:java}
> CREATE TABLE KinesisTable (
> `user_id` BIGINT,
> `arrival_time` TIMESTAMP(3) METADATA FROM 'timestamp' VIRTUAL,
> `shard_id` VARCHAR(128) NOT NULL METADATA FROM 'shard-id' VIRTUAL,
> `sequence_number` VARCHAR(128) NOT NULL METADATA FROM 'sequence-number'
> VIRTUAL
> )
> WITH (
> 'connector' = 'kinesis-legacy',
> ...
> ){code}
> We should support this for the new kinesis connector source too.
>
> h2. Success Criteria
> # *kinesis* Table API source supports *VIRTUAL* columns
> # Automated tests added to validate that the connector supports metadata.
> # Update Table API docs to indicate the bug has been fixed.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
