[
https://issues.apache.org/jira/browse/PIG-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038138#comment-14038138
]
Cheolsoo Park commented on PIG-4018:
------------------------------------
[~tmwoodruff], I ran the unit tests and found the following failures-
{code}
>>> org.apache.pig.test.TestUnionOnSchema.testUnionOnSchemaUdfTypeEvolution2
>>> org.apache.pig.test.TestUnionOnSchema.testUnionOnSchemaUdfTypeEvolution
>>> org.apache.pig.test.TestUnionOnSchema.testUnionOnSchemaIncompatibleTypes
{code}
Can you take a look at them?
> Schema validation fails with UNION ONSCHEMA
> -------------------------------------------
>
> Key: PIG-4018
> URL: https://issues.apache.org/jira/browse/PIG-4018
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.13.0
> Reporter: Travis Woodruff
> Assignee: Travis Woodruff
> Attachments: PIG-4018.patch
>
>
> When relations with differing schemas are unioned (using UNION ONSCHEMA),
> schema validation can fail with this exception:
> {{org.apache.pig.impl.plan.PlanValidationException: Logical plan invalid
> state: invalid uid -1 in schema}}
> This worked before the fix for PIG-3492.
> The merged schema (from {{LOUnion.getSchema()}}) does not contain uids for
> columns not in the schema of the first input (uids are set to -1). This is
> because only the first input's schema is used for looking up "cached" uids.
> Normally, this isn't a problem because {{UnionOnSchemaSetter}} comes along
> and fixes the missing fields.
> However, when {{ImplicitSplitInsertVisitor}} is active, it is called before
> {{UnionOnSchemaSetter}}. {{ImplicitSplitInsertVisitor}} calls
> {{schemaResetter.visit()}}, which throws the validation exception because
> {{UnionOnSchemaSetter}} has not had a chance to create the missing fields
> (and thus uids are still -1 for these fields).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
