[
https://issues.apache.org/jira/browse/PIG-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881474#action_12881474
]
Ashutosh Chauhan commented on PIG-1461:
---------------------------------------
w.r.t language I think
{code}
U = union L1, L2 using 'merge';
{code}
is better then
{code}
U = unionschema L1,L2;
{code}
Because U is indeed union with duplicated columns eliminated. User doesn't need
to learn about a new operator.
Internally for Pig, its better to avoid introducing new physical operator if we
can.
> support union operation that merges based on column names
> ---------------------------------------------------------
>
> Key: PIG-1461
> URL: https://issues.apache.org/jira/browse/PIG-1461
> Project: Pig
> Issue Type: New Feature
> Components: impl
> Affects Versions: 0.8.0
> Reporter: Thejas M Nair
> Fix For: 0.8.0
>
>
> When the data has schema, it often makes sense to union on column names in
> schema rather than the position of the columns.
> The behavior of existing union operator should remain backward compatible .
> This feature can be supported using either a new operator or extending union
> to support 'using' clause . I am thinking of having a new operator called
> either unionschema or merge . Does anybody have any other suggestions for the
> syntax ?
> example -
> L1 = load 'x' as (a,b);
> L2 = load 'y' as (b,c);
> U = unionschema L1, L2;
> describe U;
> U: {a:bytearray, b:byetarray, c:bytearray}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
