[
https://issues.apache.org/jira/browse/PIG-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ding updated PIG-1090:
------------------------------
Attachment: PIG-1090-3.patch
This patch deals with conversions between Pig Schema and the new Resource
Schema.
Given a resource schema, one calls the folllowing static method of Schema to
convert it to a Pig schema:
{code}
public static Schema getPigSchema(ResourceSchema rSchema) throws
FrontendException;
{code}
One the other hand, a Pig schema is converted to a Resource Schema by passing
it to a resource schema constructor:
{code}
public ResourceSchema(Schema pigSchema) ;
{code}
One restriction for Resource Schema is that a Bag defined by Resource Schema
must contain exactly one field of type Tuple. Ohterwise an exception will
thrown during the conversion.
Here are results from a local 'test-patch' run:
{code}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
{code}
> Update sources to reflect recent changes in load-store interfaces
> -----------------------------------------------------------------
>
> Key: PIG-1090
> URL: https://issues.apache.org/jira/browse/PIG-1090
> Project: Pig
> Issue Type: Sub-task
> Reporter: Pradeep Kamath
> Assignee: Pradeep Kamath
> Attachments: PIG-1090-2.patch, PIG-1090-3.patch, PIG-1090.patch
>
>
> There have been some changes (as recorded in the Changes Section, Nov 2 2009
> sub section of http://wiki.apache.org/pig/LoadStoreRedesignProposal) in the
> load/store interfaces - this jira is to track the task of making those
> changes under src. Changes under test will be addresses in a different jira.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
