You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/03 15:57:00 UTC

[jira] [Work logged] (BEAM-6114) SQL join selection should be done in planner, not in expansion to PTransform

     [ https://issues.apache.org/jira/browse/BEAM-6114?focusedWorklogId=305662&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-305662 ]

ASF GitHub Bot logged work on BEAM-6114:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Sep/19 15:56
            Start Date: 03/Sep/19 15:56
    Worklog Time Spent: 10m 
      Work Description: amaliujia commented on issue #9453: [BEAM-6114] Handle Unsupported Lookup Joins in BeamSql
URL: https://github.com/apache/beam/pull/9453#issuecomment-527522279
 
 
   I was on a vocation and will take a look at this PR soon.
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 305662)
    Time Spent: 4h  (was: 3h 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
>             Fix For: 2.16.0
>
>          Time Spent: 4h
>  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)