[
https://issues.apache.org/jira/browse/FLINK-23687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464219#comment-17464219
]
lincoln lee commented on FLINK-23687:
-------------------------------------
[~jingzhang] [~HunterHunter] [~straw] Glad to see the active contribution for
enhancing the commonly used lookup-join!
I'd like to share some thoughts of this:
1. Since this is a series of related improvements and include sql syntax
change, I think it's worth starting a new flip discussion.
2. Flink has always taken stream & batch unification as a design principle, so
our improvements in such a join hint also need to consider the batch scenario,
yes, we should consider the unity and applicability of the new hints on both
stream and batch, so we may need to consider whether there is a better hint
name outside of 'partitioned join'
Btw, I know that the improvements mentioned above have been in service for
years on some vendors including Alibaba's enterprise version, so we'd better
hear to more feedback.
Looking forward all these exciting improvements!
> Introduce partitioned lookup join to enforce input of LookupJoin to hash
> shuffle by lookup keys
> -----------------------------------------------------------------------------------------------
>
> Key: FLINK-23687
> URL: https://issues.apache.org/jira/browse/FLINK-23687
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: Jing Zhang
> Assignee: Jing Zhang
> Priority: Major
> Labels: pull-request-available
>
> Add Sql query hint to enable LookupJoin shuffle by join key of left input
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
