You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2011/05/13 02:24:48 UTC
[jira] [Commented] (PIG-2068) documentation of union onschema
restrictions need to to be updated
[ https://issues.apache.org/jira/browse/PIG-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032766#comment-13032766 ]
Thejas M Nair commented on PIG-2068:
------------------------------------
I mean, in 0.9 such a restriction is not there for union onschema. This is a result of the changes in PIG-1536.
> documentation of union onschema restrictions need to to be updated
> ------------------------------------------------------------------
>
> Key: PIG-2068
> URL: https://issues.apache.org/jira/browse/PIG-2068
> Project: Pig
> Issue Type: Bug
> Components: documentation
> Affects Versions: 0.9.0
> Reporter: Thejas M Nair
> Assignee: Corinne Chandel
> Fix For: 0.9.0
>
>
> The following requirement mentioned under union-onschema section is no longer applicable -
> {code}
> The data type for columns with same name in different input schemas should be compatible:
> Numeric types are compatible, and if column having same name in different input schemas have different numeric types, an implicit conversion will happen.
> Bytearray type is considered compatible with all other types, a cast will be added to convert to other type.
> Bags or tuples having different inner schema are considered incompatible.
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira