[
https://issues.apache.org/jira/browse/PIG-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Dai updated PIG-1330:
----------------------------
Status: Resolved (was: Patch Available)
Hadoop Flags: [Reviewed]
Resolution: Fixed
No unit test since this mostly a document change, no behavior will be changed
for now, just to be consistent as the code evolves. Committed to both 0.7
branch and trunk.
> Move pruned schema tracking logic from LoadFunc to core code
> ------------------------------------------------------------
>
> Key: PIG-1330
> URL: https://issues.apache.org/jira/browse/PIG-1330
> Project: Pig
> Issue Type: Improvement
> Components: impl
> Affects Versions: 0.7.0
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Fix For: 0.7.0
>
> Attachments: PIG-1330-1.patch
>
>
> Currently, LoadFunc.getSchema require a schema after column pruning. The good
> side of this is LoadFunc.getSchema matches the data it actually load. This
> gives a sense of consistency. However, by doing this, every LoadFunc need to
> keep track of the columns pruned. This is an unnecessary burden to the
> LoadFunc writer and it is very error proning. This issue is to move this
> logic from LoadFunc to Pig core. LoadFunc.getSchema then only need to return
> original schema even after pruning.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
