[
https://issues.apache.org/jira/browse/FLINK-31663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824699#comment-17824699
]
Jacky Lau commented on FLINK-31663:
-----------------------------------
[~dwysakowicz] Even though they are different functions, we need to maintain
basic behavioral consistency. In Spark, many array functions such as
array_except, array_union, and array_intersect have consistent behaviors
regarding whether duplicates are allowed. For example, otherwise users might
find the behavior to be inconsistent and tricky to use. For another example, in
Spark, functions like array_contains(array, element) and array_position(array,
element) return null when the element is null. In contrast, in Flink,
array_contains returns true if the array contains null values. However, if the
element is null, array_position returns null, which is a different behavior and
can be confusing for users. Unfortunately, the current behavior in Flink for
array_contains and array_position is not consistent, so I've submitted a PR to
correct this issue, but it has not been reviewed yet
[https://github.com/apache/flink/pull/22946] What do you think?
> Add ARRAY_EXCEPT supported in SQL & Table API
> ---------------------------------------------
>
> Key: FLINK-31663
> URL: https://issues.apache.org/jira/browse/FLINK-31663
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: luoyuxia
> Assignee: Hanyu Zheng
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
