[ 
https://issues.apache.org/jira/browse/PIG-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607189#comment-13607189
 ] 

Feng Peng commented on PIG-3222:
--------------------------------

[~daijy], thanks for looking into this. When I ran the above query, I can see 
two log string like the following, which means the program contacted the 
HiveMetastore twice. Since HCatStorer caches the results if the signature is 
the same, we should see only one metastore query here.

{noformat}
2013-03-20 02:01:02,103 [main] INFO  hive.metastore - Trying to connect to 
HiveMetaStore with URI ....
....
2013-03-20 02:01:17,733 [JobControl] INFO  hive.metastore - Trying to connect 
to HiveMetaStore with URI ...
{noformat}

[~billgraham], we basically instrumented a StoreFunc implementation to show 
what signature it gets from the framework and it showed that the same StoreFunc 
is called with different signatures. I will see if I can come up with a simple 
example.   
                
> 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
>
> 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

Reply via email to