[
https://issues.apache.org/jira/browse/FLINK-25483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser closed FLINK-25483.
----------------------------------
Resolution: Cannot Reproduce
Thanks for opening this ticket, but unfortunately I had to close it. This
ticket doesn't contain the necessary information to classify it as a bug or a
feature request. I recommend that you use the Flink user mailing list to post
your problem and get help. You can find all information at
https://flink.apache.org/community.html#mailing-lists
> 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: Improvement
> 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)
