[
https://issues.apache.org/jira/browse/TEZ-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054889#comment-14054889
]
Jeff Zhang commented on TEZ-974:
--------------------------------
[~bikassaha] This remind me of the explain function of PigServer which only
print the query plan in client side without any affect on the server side
(dry-run). We can provide similar function in TezClient to advanced users for
troubleshooting and debugging purpose. Regarding your suggestion about the
config based approach for dry-run, in this way TezClient either been used for
dry-run or for real-run, otherwise, the verify arise again. Does it make more
sense to allow users to use one TezClient for both 2 scenairos ?
And one extreme example I can see is that user call submit 2 times in client
side, it is possible to throw the exception happened in verify rather than the
DuplicateDAGName exception from server side. If the exception is from the
verify, this will confuse users.
> Support graphviz dag generation on the client
> ---------------------------------------------
>
> Key: TEZ-974
> URL: https://issues.apache.org/jira/browse/TEZ-974
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Jeff Zhang
> Attachments: Tez-974.patch
>
>
> Support generation of the dot file on the client for debugging purposes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
