[
https://issues.apache.org/jira/browse/PIG-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607904#comment-13607904
]
Feng Peng commented on PIG-3222:
--------------------------------
Modified the test class to add instruments for all StoreFuncInterface functions
and here is the sequence called on the frontend,
The first number is an instance id. We can see that:
* the storer is instantiated three times
* the first instance is assigned a different signature than the later two
* the 2nd instance generates two different Job objects in two different
setStoreLocation calls
{noformat}
[0]setStoreFuncUDFContextSignature(samples_1-3)
[0]relToAbsPathForStoreLocation(testdb.samples,hdfs://..)
[1]setStoreFuncUDFContextSignature(samples_1-6)
[1]checkSchema(number:int)
[1]setStoreLocation(testdb.samples,Job@1817929566)
[1]getOutputFormat
[1]setStoreLocation(testdb.samples,Job@603950563)
[2]setStoreFuncUDFContextSignature(samples_1-6)
[2]setStoreLocation(testdb.samples,Job@1203999762)
[2]getOutputFormat
{noformat}
> New UDFContextSignature assignments in Pig 0.11 breaks HCatalog.HCatStorer
> ---------------------------------------------------------------------------
>
> Key: PIG-3222
> URL: https://issues.apache.org/jira/browse/PIG-3222
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: 0.11
> Reporter: Feng Peng
> Labels: hcatalog
> Attachments: PigStorerDemo.java
>
>
> Pig 0.11 assigns different UDFContextSignature for different invocations of
> the same load/store statement. This change breaks the HCatStorer which
> assumes all front-end and back-end invocations of the same store statement
> has the same UDFContextSignature so that it can read the previously stored
> information correctly.
> The related HCatalog code is in
> https://svn.apache.org/repos/asf/incubator/hcatalog/branches/branch-0.5/hcatalog-pig-adapter/src/main/java/org/apache/hcatalog/pig/HCatStorer.java
> (the setStoreLocation() function).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
