Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Thu, 2 Nov 2017 18:41:00 +0000 (UTC)
From: "Travis Woodruff (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.13115706.1509647807000.134881.1509648060830@Atlassian.JIRA>
In-Reply-To: <JIRA.13115706.1509647807000@Atlassian.JIRA>
References: <JIRA.13115706.1509647807000@Atlassian.JIRA> <JIRA.13115706.1509647807761@jira-lw-us.apache.org>
Subject: [jira] [Updated] (PIG-5312) Uids not set in inner schemas after
 UNION ON_SCHEMA
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Nov 2017 18:41:05 -0000


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

Travis Woodruff updated PIG-5312:
---------------------------------
    Assignee:     (was: Travis Woodruff)
      Status: Patch Available  (was: Open)

> Uids not set in inner schemas after UNION ON_SCHEMA
> ---------------------------------------------------
>
>                 Key: PIG-5312
>                 URL: https://issues.apache.org/jira/browse/PIG-5312
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.17.0, 0.16.0
>            Reporter: Travis Woodruff
>            Priority: Normal
>         Attachments: PIG-5312.patch
>
>
> Ran into a failure with a script of the form:
> {code}
> u = union on_schema x, y;  -- schema: (a, b: {(m:int, n: chararray)})
> z = foreach u {
>     i = foreach b generate m + 5;
>     generate a, i;
> }
> {code}
> The issue ended up being that {{LOUnion}} is not setting uids on inner schemas. This means that uids on inner schema fields are all -1, so when {{ProjectExpression.getFieldSchema()}} tries to look up the fields in the inner select from the inner schema, all the fields match, and the last field's schema ends up being returned. In the example above this causes {{TypeCheckingExpVisitor.addCastsToNumericBinExpression()}} to fail for the addition operator (since the returned field schema is a chararray).
> This only seems to affect the schema, so I don't think this should cause bad data to be produced.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)