[jira] [Updated] (FLINK-12079) Add support for generating optimized logical plan for join on batch
[
https://issues.apache.org/jira/browse/FLINK-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
godfrey he updated FLINK-12079:
---
Description:
Currently, there are 3 types of batch physical join nodes:
{{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
{{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
join to appropriate physical join.
a logical join
* can be converted to {{BatchExecHashJoin}} if there exists at least one
equal-join condition and ShuffleHashJoin or BroadcastHashJoin are enabled,
* can be converted to {{BatchExecSortMergeJoin}} if there exists at least one
equal-join condition and SortMergeJoin is enabled,
* can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is enabled
or one of join input sides returns at most a single row.
was:
Currently, there are 3 types of batch physical join nodes:
{{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
{{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
join to appropriate physical join.
a logical join
* can be converted to {{BatchExecHashJoin}} if join keys are not empty and
ShuffleHashJoin or BroadcastHashJoin are enabled,
* can be converted to {{BatchExecSortMergeJoin}} if join keys are not empty and
SortMergeJoin is enabled,
* can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is enabled
or one of join input sides returns at most a single row.
> Add support for generating optimized logical plan for join on batch
> ---
>
> Key: FLINK-12079
> URL: https://issues.apache.org/jira/browse/FLINK-12079
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
>Reporter: godfrey he
>Assignee: godfrey he
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, there are 3 types of batch physical join nodes:
> {{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
> {{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
> join to appropriate physical join.
> a logical join
> * can be converted to {{BatchExecHashJoin}} if there exists at least one
> equal-join condition and ShuffleHashJoin or BroadcastHashJoin are enabled,
> * can be converted to {{BatchExecSortMergeJoin}} if there exists at least one
> equal-join condition and SortMergeJoin is enabled,
> * can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is
> enabled or one of join input sides returns at most a single row.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-12079) Add support for generating optimized logical plan for join on batch
[
https://issues.apache.org/jira/browse/FLINK-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-12079:
---
Labels: pull-request-available (was: )
> Add support for generating optimized logical plan for join on batch
> ---
>
> Key: FLINK-12079
> URL: https://issues.apache.org/jira/browse/FLINK-12079
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
>Reporter: godfrey he
>Assignee: godfrey he
>Priority: Major
> Labels: pull-request-available
>
> Currently, there are 3 types of batch physical join nodes:
> {{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
> {{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
> join to appropriate physical join.
> a logical join
> * can be converted to {{BatchExecHashJoin}} if join keys are not empty and
> ShuffleHashJoin or BroadcastHashJoin are enabled,
> * can be converted to {{BatchExecSortMergeJoin}} if join keys are not empty
> and SortMergeJoin is enabled,
> * can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is
> enabled or one of join input sides returns at most a single row.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-12079) Add support for generating optimized logical plan for join on batch
[
https://issues.apache.org/jira/browse/FLINK-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
godfrey he updated FLINK-12079:
---
Description:
Currently, there are 3 types of batch physical join nodes:
{{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
{{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
join to appropriate physical join.
a logical join
* can be converted to {{BatchExecHashJoin}} if join keys are not empty and
ShuffleHashJoin or BroadcastHashJoin are enabled,
* can be converted to {{BatchExecSortMergeJoin}} if join keys are not empty and
SortMergeJoin is enabled,
* can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is enabled
or one of join input sides returns at most a single row.
was:
Currently, there are 3 types of batch physical join nodes:
{{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
{{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
join to appropriate physical join.
a logical join
* can be converted to {{BatchExecHashJoin}} if join keys are not empty and
ShuffleHashJoin or BroadcastHashJoin are enabled,
* can be converted to {{BatchExecSortMergeJoin}} if join keys are not empty and
SortMergeJoin is enabled,
* can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is enabled
or one of join input sides returns at most a single row.
> Add support for generating optimized logical plan for join on batch
> ---
>
> Key: FLINK-12079
> URL: https://issues.apache.org/jira/browse/FLINK-12079
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
>Reporter: godfrey he
>Assignee: godfrey he
>Priority: Major
>
> Currently, there are 3 types of batch physical join nodes:
> {{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
> {{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
> join to appropriate physical join.
> a logical join
> * can be converted to {{BatchExecHashJoin}} if join keys are not empty and
> ShuffleHashJoin or BroadcastHashJoin are enabled,
> * can be converted to {{BatchExecSortMergeJoin}} if join keys are not empty
> and SortMergeJoin is enabled,
> * can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is
> enabled or one of join input sides returns at most a single row.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-12079) Add support for generating optimized logical plan for join on batch
[
https://issues.apache.org/jira/browse/FLINK-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
godfrey he updated FLINK-12079:
---
Description:
Currently, there are 3 types of batch physical join nodes:
{{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
{{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
join to appropriate physical join.
a logical join
* can be converted to {{BatchExecHashJoin}} if join keys are not empty and
ShuffleHashJoin or BroadcastHashJoin are enabled,
* can be converted to {{BatchExecSortMergeJoin}} if join keys are not empty and
SortMergeJoin is enabled,
* can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is enabled
or one of join input sides returns at most a single row.
was:
Currently, there are 3 types of batch physical join nodes:
{{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
{{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
join to appropriate physical join.
a logical join
* can be converted to {{BatchExecHashJoin}} if join keys are not empty and
ShuffleHashJoin or BroadcastHashJoin are enabled,
* can be converted to {{BatchExecSortMergeJoin}} if join keys are not empty and
SortMergeJoin is enabled,
* can be converted to {{BatchExecNestedLoopJoinRule}} if NestedLoopJoin is
enabled or one of join input sides returns at most a single row.
> Add support for generating optimized logical plan for join on batch
> ---
>
> Key: FLINK-12079
> URL: https://issues.apache.org/jira/browse/FLINK-12079
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
>Reporter: godfrey he
>Assignee: godfrey he
>Priority: Major
>
> Currently, there are 3 types of batch physical join nodes:
> {{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
> {{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
> join to appropriate physical join.
> a logical join
> * can be converted to {{BatchExecHashJoin}} if join keys are not empty and
> ShuffleHashJoin or BroadcastHashJoin are enabled,
> * can be converted to {{BatchExecSortMergeJoin}} if join keys are not empty
> and SortMergeJoin is enabled,
> * can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is
> enabled or one of join input sides returns at most a single row.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
