[
https://issues.apache.org/jira/browse/FLINK-25483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472095#comment-17472095
]
Martijn Visser commented on FLINK-25483:
----------------------------------------
[~empcl] In your SQL statement, you are explicitly selecting the values from
fields a, b and c. You are not filtering for any null values, so you are
accepting that a null value can be returned. Changing this behavior means that
changing how the SQL standard defines it. With regards to such a function being
helpful to other users, I haven't seen requests for such a capability so that
implies that the functionality works as expected (because users actually want
to insert null values) or because the mentioned alternatives are working for
them.
> 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)
