You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2022/04/13 06:28:07 UTC

[jira] [Updated] (FLINK-19432) Whether to capture the updates which don't change any monitored columns

     [ https://issues.apache.org/jira/browse/FLINK-19432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yun Gao updated FLINK-19432:
----------------------------
    Fix Version/s: 1.16.0

> Whether to capture the updates which don't change any monitored columns
> -----------------------------------------------------------------------
>
>                 Key: FLINK-19432
>                 URL: https://issues.apache.org/jira/browse/FLINK-19432
>             Project: Flink
>          Issue Type: Improvement
>          Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
>    Affects Versions: 1.11.1
>            Reporter: shizhengchao
>            Priority: Minor
>              Labels: auto-deprioritized-major
>             Fix For: 1.15.0, 1.16.0
>
>
> with `debezium-json` and `canal-json`: 
> Whether to capture the updates which don't change any monitored columns. This may happen if the monitored columns (columns defined in Flink SQL DDL) is a subset of the columns in database table.  We can provide an optional option， default 'true', which means all the updates will be captured. You can set to 'false' to only capture changed updates



--
This message was sent by Atlassian Jira
(v8.20.1#820001)