[
https://issues.apache.org/jira/browse/FLINK-39636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo de Morais closed FLINK-39636.
-------------------------------------
Resolution: Fixed
Fixed in: bca2c0a6170adbbf39cfaf4327ec368f003e4f40,
340fbf879fd3e03dea7b37f7c28c6c404db21f65,
32f9e60eb9d7c33bac4fb3f91dc0200f03507c0c,
e400c2c221368e98e80d5589cacbcb0b1585ba66,
c033b17fae27117fbfc6b007348e9499d7830023
> Add "produces_full_deletes" parameter in TO_CHANGELOG
> -----------------------------------------------------
>
> Key: FLINK-39636
> URL: https://issues.apache.org/jira/browse/FLINK-39636
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Gustavo de Morais
> Assignee: Ramin Gharib
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.4.0
>
>
> We currently always require full deletes in TO_CHANGELOG by using the PTF
> trait "StaticArgumentTrait.REQUIRE_FULL_DELETE". That means, if we have a
> source containing partial deletes (as kafka does) we'll add a
> ChangelogNormalize to the pipeline to build full delete events out of partial
> deletes.
> By adding the produces_full_deletes param, we can make this trait conditional
> and check and only require full deletes if we have to produce full deletes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
