[jira] [Commented] (TEZ-3385) DAGClient API should be accessible outside of DAG submission
[ https://issues.apache.org/jira/browse/TEZ-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150750#comment-16150750 ] Rohini Palaniswamy commented on TEZ-3385: - bq. Is this only for DAGClient, or for TezClient only Both should be accessible. But created this jira for DAGClient. > DAGClient API should be accessible outside of DAG submission > > > Key: TEZ-3385 > URL: https://issues.apache.org/jira/browse/TEZ-3385 > Project: Apache Tez > Issue Type: New Feature >Reporter: Rohini Palaniswamy > > In PIG-4958, I had to resort to > DAGClient client = new DAGClientImpl(appId, dagID, new > TezConfiguration(conf), null); > This is not good as DAGClientImpl is a internal class and not something users > should be referring to. Tez needs to have an API to give DAGClient given the > appId, dagID and configuration. This is something basic like > JobClient.getJob(String jobID). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (TEZ-3385) DAGClient API should be accessible outside of DAG submission
[ https://issues.apache.org/jira/browse/TEZ-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149692#comment-16149692 ] Sergey Shelukhin commented on TEZ-3385: --- Is this only for DAGClient, or for TezClient only? Hive might be interested in the latter for HA/multi-HS2 work (transferring Tez sessions between HS2s). cc [~hagleitn] > DAGClient API should be accessible outside of DAG submission > > > Key: TEZ-3385 > URL: https://issues.apache.org/jira/browse/TEZ-3385 > Project: Apache Tez > Issue Type: New Feature >Reporter: Rohini Palaniswamy > > In PIG-4958, I had to resort to > DAGClient client = new DAGClientImpl(appId, dagID, new > TezConfiguration(conf), null); > This is not good as DAGClientImpl is a internal class and not something users > should be referring to. Tez needs to have an API to give DAGClient given the > appId, dagID and configuration. This is something basic like > JobClient.getJob(String jobID). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
