[
https://issues.apache.org/jira/browse/FLINK-32188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726597#comment-17726597
]
Jark Wu commented on FLINK-32188:
---------------------------------
Yes, I think your fix is fine. The function name "array" in
BuiltInFunctionDefinition is not equal to "ARRAY_VALUE_CONSTRUCTOR", I think
that's why we can't find the function via {{lookupFunction}}.
> Does the custom connector not support pushing down "where" query predicates
> to query fields of array type？
> ----------------------------------------------------------------------------------------------------------
>
> Key: FLINK-32188
> URL: https://issues.apache.org/jira/browse/FLINK-32188
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.12.2, 1.17.0, 1.16.1
> Reporter: Xin Chen
> Priority: Major
> Attachments: image-2023-05-25-17-16-02-288.png,
> image-2023-05-25-20-44-08-834.png, image-2023-05-25-20-44-47-581.png,
> screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png,
> screenshot-5.png, screenshot-6.png, screenshot-7.png
>
>
> When I customized a data source connector which assumed as image-connector, I
> found that when creating a table with ddl, I specified a field URL as an
> array type. When submitting an SQL task with Flink, I specified query this
> field as a fixed array. For example, select * from image source where
> URL=ARRAY ['/flink. jpg', '/flink_1. jpg'], but it couldn't obtain the
> corresponding predicate filters at all.
> Does the custom connector not support to query fields of array type with
> "where"？
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
