[jira] Updated: (PIG-1239) PigContext.connect() should not create a jobClient and jobClient should be created on demand when needed

["Pradeep Kamath (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PIG-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pradeep Kamath updated PIG-1239:
--------------------------------

    Attachment: PIG-1239-load-store-redesign-branch.patch
                PIG-1239-branch-0.6.patch

Attached patches for branch-0.6 and load-store-redesign branch.

Changes are:
 * PigContext.connect() does not create a JobClient - instead it creates and holds a JobConf object - callers have been changed to use the JobConf and create a JobClient 
 * On the load-store-redesign branch, POMergeJoin no longer does a pc.connect since it is no longer needed

> PigContext.connect() should not create a jobClient and jobClient should be created on demand when needed
> --------------------------------------------------------------------------------------------------------
>
>                 Key: PIG-1239
>                 URL: https://issues.apache.org/jira/browse/PIG-1239
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Pradeep Kamath
>            Assignee: Pradeep Kamath
>             Fix For: 0.6.0, 0.7.0
>
>         Attachments: PIG-1239-branch-0.6.patch, PIG-1239-load-store-redesign-branch.patch
>
>
> PigContext.connect() currently connects to the jobtracker and creates a JobClient - this causes issue in POMergeJoin/POFRJoin wherein these connections to the jobtracker are made from each map task. The creation of the JobClient is not necessary in PigContext.connect() and a JobClient should be created on demand where it is needed instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.