[
https://issues.apache.org/jira/browse/BEAM-6810?focusedWorklogId=212067&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-212067
]
ASF GitHub Bot logged work on BEAM-6810:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Mar/19 21:34
Start Date: 12/Mar/19 21:34
Worklog Time Spent: 10m
Work Description: kanterov commented on issue #8035: [BEAM-6810] Disable
CalcRemoveRule to fix trivial projections
URL: https://github.com/apache/beam/pull/8035#issuecomment-472190441
@amaliujia thanks! Agree, I discovered this issue by an internal test suite.
I was looking into
[CALCITE-1584](https://issues.apache.org/jira/browse/CALCITE-1584), it seems
that Drill had similar issues, but I didn't check how they fixed it. Let's
follow up and see how we can fix that in the right way.
I was surprised to read:
> Calcite doesn't promise to retain field names. 95% of the time it can and
does, but 5% of the time it really can't retain field names without seriously
compromising the Volcano engine.
----------------------------------------------------------------
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: 212067)
Time Spent: 40m (was: 0.5h)
> [SQL] Plan optimizer eliminates aliasing in trivial projections
> ---------------------------------------------------------------
>
> Key: BEAM-6810
> URL: https://issues.apache.org/jira/browse/BEAM-6810
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql
> Affects Versions: 2.11.0
> Reporter: Gleb Kanterov
> Assignee: Gleb Kanterov
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Trivial programs project precisely their input fields, without dropping or
> re-ordering them. The simplest example is:
> {code}
> SELECT * FROM PCOLLECTION
> {code}
> Given input PCollection with a schema `c_int64: BIGINT` following query
> should result in PCollection with a schema `abc: BIGINT`, however, due to a
> bug in query optimization, it results in `c_int64: BIGINT`
> {code}
> SELECT c_int64 as abc FROM PCOLLECTION
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
