[jira] [Commented] (PIG-3539) Pig should be able to submit multiple DAG

["Cheolsoo Park (JIRA)" <ji...@apache.org>]

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

Cheolsoo Park commented on PIG-3539:
------------------------------------

[~daijy], I see compilation errors (easy to fix) against Tez trunk-
{code}
    [javac] /Users/cheolsoop/workspace/pig/src/org/apache/pig/backend/hadoop/executionengine/tez/TezJob.java:80: getDAGStatus() in org.apache.tez.dag.api.client.DAGClient cannot be applied to (<nulltype>)
    [javac]                 dagStatus = dagClient.getDAGStatus(null);
    [javac]  
 
    [javac] /Users/cheolsoop/workspace/pig/src/org/apache/pig/backend/hadoop/executionengine/tez/TezSessionManager.java:87: cannot find symbol
    [javac] symbol  : constructor AMConfiguration(<nulltype>,java.util.Map<java.lang.String,org.apache.hadoop.yarn.api.records.LocalResource>,org.apache.tez.dag.api.TezConfiguration,<nulltype>)
    [javac] location: class org.apache.tez.client.AMConfiguration
    [javac]         AMConfiguration amConfig = new AMConfiguration(null, resources, tezConf, null);
    [javac]
{code}

Do you mind uploading the patch to the RB? Let's get it reviewed/committed.

> Pig should be able to submit multiple DAG
> -----------------------------------------
>
>                 Key: PIG-3539
>                 URL: https://issues.apache.org/jira/browse/PIG-3539
>             Project: Pig
>          Issue Type: Sub-task
>          Components: tez
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>             Fix For: tez-branch
>
>         Attachments: PIG-3539-1.patch
>
>
> There could be several scenario Pig want to submit multiple DAG:
> 1. a blocking operator in grunt
> 2. a blocking operator in script (exec, fs)
> 3. break a DAG into two for possible inner DAG optimization
> Pig should use TezSession so that we can reuse AM. TezSession should be a thread local variable. For those who use Pig Java API, they will use the same AM within a thread, but different AM in another thread.



--
This message was sent by Atlassian JIRA
(v6.1#6144)