hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chao Wang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-1269) [Zebra] Restrict schema definition for collection
Date Thu, 11 Mar 2010 20:06:27 GMT

    [ https://issues.apache.org/jira/browse/PIG-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844212#action_12844212
] 

Chao Wang commented on PIG-1269:
--------------------------------

Patch looks good +1

> [Zebra] Restrict schema definition for collection
> -------------------------------------------------
>
>                 Key: PIG-1269
>                 URL: https://issues.apache.org/jira/browse/PIG-1269
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>             Fix For: 0.7.0
>
>         Attachments: zebra.0310
>
>
> Currently Zebra grammar for schema definition for collection field allows many types
of definition. To reduce complexity and remove ambiguity, and more importantly, to make the
meta data more representative of the actual data instances, the grammar rules need to be changed.
Only a record type is allowed and required for collection definition. Thus,  fieldName:collection(record(c1:int,
c2:string)) is legal, while fieldName:collection(c1:int, c2:string), fieldName:collection(f:record(c1:int,
c2:string)), fieldName:collection(c1:int), or feildName:collection(int) is illegal.
> This will have some impact on existing Zebra M/R programs or Pig scripts that use Zebra.
Schema acceptable in previous release now may become illegal because of this change. This
should be clearly documented.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message