You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "xiaogang zhou (Jira)" <ji...@apache.org> on 2020/10/28 08:21:00 UTC

[jira] [Comment Edited] (FLINK-19847) Can we create a fast support on the Nested table join?

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

xiaogang zhou edited comment on FLINK-19847 at 10/28/20, 8:20 AM:
------------------------------------------------------------------

In our situation, we use a Asynclookup for the redis and some inner rpc service. we combine multikey lookup to save the network cost. so the DDL uses the array type. 

when i try to join on array, some exception happens. and I notice the todo. looks like something need to be done in the 

extractConstantField? 


was (Author: zhoujira86):
In our situation, we use a Asynclookup for the redis and some inner rpc service. we combine multikey lookup to save the network cost. so the DDL uses the array type. 

where i try to join on array, some exception happens. and I notice the todo. looks like something need to be done in the 

extractConstantField? 

> Can we create a fast support on the Nested table join?
> ------------------------------------------------------
>
>                 Key: FLINK-19847
>                 URL: https://issues.apache.org/jira/browse/FLINK-19847
>             Project: Flink
>          Issue Type: Wish
>          Components: API / DataStream
>    Affects Versions: 1.11.1
>            Reporter: xiaogang zhou
>            Priority: Major
>
> In CommonLookupJoin, one TODO is 
> support nested lookup keys in the future,
> // currently we only support top-level lookup keys
>  
> can we create a fast support on the Array join? thx



--
This message was sent by Atlassian Jira
(v8.3.4#803005)