[
https://issues.apache.org/jira/browse/BEAM-10783?focusedWorklogId=473419&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-473419
]
ASF GitHub Bot logged work on BEAM-10783:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Aug/20 19:29
Start Date: 21/Aug/20 19:29
Worklog Time Spent: 10m
Work Description: amaliujia commented on pull request #12648:
URL: https://github.com/apache/beam/pull/12648#issuecomment-678454929
Have you try this PR internally to see whether there is a regression on the
WITH clause support?
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 473419)
Remaining Estimate: 0h
Time Spent: 10m
> ZetaSQL failed on WITH queries because wrong ref column index calculated in
> JoinScanWithRefConverter
> ----------------------------------------------------------------------------------------------------
>
> Key: BEAM-10783
> URL: https://issues.apache.org/jira/browse/BEAM-10783
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql-zetasql
> Reporter: Robin Qiu
> Assignee: Robin Qiu
> Priority: P2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some WITH queries, like:
> WITH t1 AS (select 1 AS k), t2 AS (select 1 AS k), t3 AS (select 1 AS k)
> SELECT COUNT\(*\)
> FROM t1 JOIN t3 USING (k)
> failed on ZetaSQL because how column index is calculated in
> JoinScanWithRefConverter is not correct.
>
> In fact, the other converter responsible for JOINs, JoinScanConverter, has
> the correct implementation, and that works fine for JOINs that has reference
> to WITH queries. So I believe we should delete the incorrect
> JoinScanWithRefConverter class and move to the other one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
