[ https://issues.apache.org/jira/browse/FLINK-25483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471000#comment-17471000 ]
陈磊 commented on FLINK-25483: ---------------------------- [~MartijnVisser] In fact, I don't understand why after doing this, it will change the way to follow the SQL standard, and the behavior of the ES connector is inconsistent with other connectors. In addition, I think the improvement of the function is more conducive to the use of users. > 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)