[jira] Commented: (PIG-986) [zebra] Zebra Column Group Naming Support
[ https://issues.apache.org/jira/browse/PIG-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764407#action_12764407 ] Hadoop QA commented on PIG-986: --- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12421692/ColumnGroupName.patch against trunk revision 823693. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 44 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/70/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/70/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/70/console This message is automatically generated. > [zebra] Zebra Column Group Naming Support > - > > Key: PIG-986 > URL: https://issues.apache.org/jira/browse/PIG-986 > Project: Pig > Issue Type: New Feature > Components: impl >Affects Versions: 0.4.0 >Reporter: Chao Wang >Assignee: Chao Wang > Fix For: 0.6.0 > > Attachments: ColumnGroupName.patch, ColumnGroupName.patch, > ColumnGroupName.patch > > > We introduce column group name to Zebra and make it a first-class citizen in > Zebra. This can ease management of column groups. > We plan to introduce an "as" clause for column group name in Zebra's syntax. > Functional Specifications: > 1) Column group names are optional. For column groups which do not have a > user-provided name, Zebra will assign some default column group names > internally that is unique for that table - CG0, CG1, CG2 ... Note: If CGx is > used by user, then it can not be used for internal names. > 2) We introduce an "AS" clause in Zebra's syntax for column group names. If > it occurs, it has to immediately follow [ ]. For example, "[a1, a2] as PI > secure by user:joe group:secure perm:640; [a3, a4] as General compress by > lzo". Note that keyword "AS" is case insensitive. > 3) Column group names are unique within one table and are case sensitive, > i.e., c1 and C1 are different. > 4) Column group names will be used as the physical column group directory > path names. > 5) Zebra V2 will support dropColumnGroup by column group names (will > integrate with Raghu's A29 drop column work). > 6) Zebra V2 can support backward compatibility (If there are Zebra V1 created > tables in production when V2 is released). More specifically, this means that > Zebra V2 can load from V1-created tables and do dropColumnGroup on it. > 7) Does NOT support renaming. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-986) [zebra] Zebra Column Group Naming Support
[ https://issues.apache.org/jira/browse/PIG-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764247#action_12764247 ] Yan Zhou commented on PIG-986: -- This patch actually does not depend upon the the latest patch, "Bugs-2.patch", in Pig-991even though that patch came after this patch. Raghu, could you do us a last favor of commiting this? Thanks. > [zebra] Zebra Column Group Naming Support > - > > Key: PIG-986 > URL: https://issues.apache.org/jira/browse/PIG-986 > Project: Pig > Issue Type: New Feature > Components: impl >Affects Versions: 0.4.0 >Reporter: Chao Wang >Assignee: Chao Wang > Fix For: 0.6.0 > > Attachments: ColumnGroupName.patch, ColumnGroupName.patch, > ColumnGroupName.patch > > > We introduce column group name to Zebra and make it a first-class citizen in > Zebra. This can ease management of column groups. > We plan to introduce an "as" clause for column group name in Zebra's syntax. > Functional Specifications: > 1) Column group names are optional. For column groups which do not have a > user-provided name, Zebra will assign some default column group names > internally that is unique for that table - CG0, CG1, CG2 ... Note: If CGx is > used by user, then it can not be used for internal names. > 2) We introduce an "AS" clause in Zebra's syntax for column group names. If > it occurs, it has to immediately follow [ ]. For example, "[a1, a2] as PI > secure by user:joe group:secure perm:640; [a3, a4] as General compress by > lzo". Note that keyword "AS" is case insensitive. > 3) Column group names are unique within one table and are case sensitive, > i.e., c1 and C1 are different. > 4) Column group names will be used as the physical column group directory > path names. > 5) Zebra V2 will support dropColumnGroup by column group names (will > integrate with Raghu's A29 drop column work). > 6) Zebra V2 can support backward compatibility (If there are Zebra V1 created > tables in production when V2 is released). More specifically, this means that > Zebra V2 can load from V1-created tables and do dropColumnGroup on it. > 7) Does NOT support renaming. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-986) [zebra] Zebra Column Group Naming Support
[ https://issues.apache.org/jira/browse/PIG-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761744#action_12761744 ] Hadoop QA commented on PIG-986: --- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12421161/ColumnGroupName.patch against trunk revision 821101. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 44 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/58/console This message is automatically generated. > [zebra] Zebra Column Group Naming Support > - > > Key: PIG-986 > URL: https://issues.apache.org/jira/browse/PIG-986 > Project: Pig > Issue Type: New Feature > Components: impl >Affects Versions: 0.4.0 >Reporter: Chao Wang >Assignee: Chao Wang > Fix For: 0.6.0 > > Attachments: ColumnGroupName.patch > > > We introduce column group name to Zebra and make it a first-class citizen in > Zebra. This can ease management of column groups. > We plan to introduce an "as" clause for column group name in Zebra's syntax. > Functional Specifications: > 1) Column group names are optional. For column groups which do not have a > user-provided name, Zebra will assign some default column group names > internally that is unique for that table - CG0, CG1, CG2 ... Note: If CGx is > used by user, then it can not be used for internal names. > 2) We introduce an "AS" clause in Zebra's syntax for column group names. If > it occurs, it has to immediately follow [ ]. For example, "[a1, a2] as PI > secure by user:joe group:secure perm:640; [a3, a4] as General compress by > lzo". Note that keyword "AS" is case insensitive. > 3) Column group names are unique within one table and are case sensitive, > i.e., c1 and C1 are different. > 4) Column group names will be used as the physical column group directory > path names. > 5) Zebra V2 will support dropColumnGroup by column group names (will > integrate with Raghu's A29 drop column work). > 6) Zebra V2 can support backward compatibility (If there are Zebra V1 created > tables in production when V2 is released). More specifically, this means that > Zebra V2 can load from V1-created tables and do dropColumnGroup on it. > 7) Does NOT support renaming. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
