[ 
https://issues.apache.org/jira/browse/FLINK-32188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726118#comment-17726118
 ] 

Xin Chen commented on FLINK-32188:
----------------------------------

DDL and query sql like as:
{code:java}
tableEnv.executeSql("CREATE TABLE IF NOT EXISTS image_source (\n" +
                "        url ARRAY<STRING>,\n" + //ARRAY<STRING>
                "        image ARRAY<BYTES>,\n" + //ARRAY<BYTES>    
                "        proc AS proctime()\n" +
                "        ) WITH (\n" +
                "        'connector' = 'image-connector',\n" +
                "        'ip'='11.11.11.11',\n" +
                "        'port'='11111',\n" +
                "        )");
String s3 = "select * from image_source "
                + "where url = ARRAY['/flink.jpg', '/flink_1.jpg']";
        TableResult result = tableEnv.executeSql(s3);//s3
        result.print();

{code}



> 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: Technical Debt
>          Components: Table SQL / Planner
>    Affects Versions: 1.12.2, 1.17.0, 1.16.1
>            Reporter: Xin Chen
>            Priority: Major
>
> 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 I found that 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)

Reply via email to