[
https://issues.apache.org/jira/browse/BEAM-6114?focusedWorklogId=298923&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-298923
]
ASF GitHub Bot logged work on BEAM-6114:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Aug/19 19:21
Start Date: 21/Aug/19 19:21
Worklog Time Spent: 10m
Work Description: rahul8383 commented on pull request #9395: [BEAM-6114]
Calcite Rules to Select Type of Join in BeamSQL
URL: https://github.com/apache/beam/pull/9395
Calcite Rules:
BeamSideInputJoinRule, BeamSideInputLookupJoinRule, BeamStandardJoinRule
are added to select the type of Join instead of Selecting the Join in the
Expansion of PTransform.
Since SideInputLookupJoin condition may collide with SideInputJoin and
StandardJoin, if any of the inputs of Join is Seekable, BeamSideInputJoinRule
and BeamStandardJoinRule will not be matched.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 298923)
Time Spent: 1h (was: 50m)
> SQL join selection should be done in planner, not in expansion to PTransform
> ----------------------------------------------------------------------------
>
> Key: BEAM-6114
> URL: https://issues.apache.org/jira/browse/BEAM-6114
> Project: Beam
> Issue Type: Improvement
> Components: dsl-sql
> Reporter: Kenneth Knowles
> Assignee: Rahul Patwari
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently Beam SQL joins all go through a single physical operator which has
> a single PTransform that does all join algorithms based on properties of its
> input PCollections as well as the relational algebra.
> A first step is to make the needed information part of the relational
> algebra, so it can choose a PTransform based on that, and the PTransforms can
> be simpler.
> Second step is to have separate (physical) relational operators for different
> join algorithms.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
