[ https://issues.apache.org/jira/browse/PIG-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782759#action_12782759 ]
Dmitriy V. Ryaboy commented on PIG-760: --------------------------------------- Argh. I totally missed Alan's comment before creating this new patch. To address Alan's concerns: the patch doesn't break any current interfaces, just adds a few new ones, which aren't "public". I can commit to updating this issue as the definitions of the interfaces change. Where my implementation of the spec differs from the code in the load-store redesign branch, I believe it's because I am actually writing code that uses stats and schema loaders, and these changes should be considered for the branch. > Serialize schemas for PigStorage() and other storage types. > ----------------------------------------------------------- > > Key: PIG-760 > URL: https://issues.apache.org/jira/browse/PIG-760 > Project: Pig > Issue Type: New Feature > Reporter: David Ciemiewicz > Assignee: Dmitriy V. Ryaboy > Fix For: 0.7.0 > > Attachments: pigstorageschema-2.patch, pigstorageschema.patch, > pigstorageschema_3.patch > > > I'm finding PigStorage() really convenient for storage and data interchange > because it compresses well and imports into Excel and other analysis > environments well. > However, it is a pain when it comes to maintenance because the columns are in > fixed locations and I'd like to add columns in some cases. > It would be great if load PigStorage() could read a default schema from a > .schema file stored with the data and if store PigStorage() could store a > .schema file with the data. > I have tested this out and both Hadoop HDFS and Pig in -exectype local mode > will ignore a file called .schema in a directory of part files. > So, for example, if I have a chain of Pig scripts I execute such as: > A = load 'data-1' using PigStorage() as ( a: int , b: int ); > store A into 'data-2' using PigStorage(); > B = load 'data-2' using PigStorage(); > describe B; > describe B should output something like { a: int, b: int } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.