You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Gleb Kanterov (JIRA)" <ji...@apache.org> on 2019/03/12 10:56:00 UTC

[jira] [Updated] (BEAM-6810) [SQL] Plan optimizer eliminates aliasing in trivial projections

     [ https://issues.apache.org/jira/browse/BEAM-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gleb Kanterov updated BEAM-6810:
--------------------------------
    Description: 
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}

  was:
Trivial projection is a projection that uses all input columns and doesn't re-order them. 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}


> [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
>
>
> 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)