You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "陈磊 (Jira)" <ji...@apache.org> on 2022/01/02 10:38:00 UTC

[jira] [Updated] (FLINK-25483) When FlinkSQL writes ES, it will not write and update the null value field

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

陈磊 updated FLINK-25483:
-----------------------
    Issue Type: New Feature  (was: Improvement)

> When FlinkSQL writes ES, it will not write and update the null value field
> --------------------------------------------------------------------------
>
>                 Key: FLINK-25483
>                 URL: https://issues.apache.org/jira/browse/FLINK-25483
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / Ecosystem
>            Reporter: 陈磊
>            Priority: Minor
>
> Using Flink SQL to consume Kafka to write ES, sometimes some fields do not exist, and those that do not exist do not want to write ES, how to deal with this situation?
> For example: the source data has 3 fields, a, b, c
> insert into table2
> select
> a,b,c
> from table1
> When b=null, only hope to write a and c
> When c=null, only hope to write a and b
>  



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