[
https://issues.apache.org/jira/browse/TEZ-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated TEZ-4333:
------------------------------
Description:
Currently, tez.generate.debug.artifacts save a serialized protobuf file, which
is hard to read because it just encodes the user payload. At the same time, tez
AM logs a readable json file into the tez AM logs but only in DEBUG level. I'm
proposing that tez.generate.debug.artifacts could write this readable json into
a separated dag json file, this way:
1. we can use tez.generate.debug.artifacts to create one more useful file
2. don't have to set AM log level to DEBUG if we're only interested in the dag
plan
> Debug artifacts can include DAG plan in json format
> ---------------------------------------------------
>
> Key: TEZ-4333
> URL: https://issues.apache.org/jira/browse/TEZ-4333
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
>
> Currently, tez.generate.debug.artifacts save a serialized protobuf file,
> which is hard to read because it just encodes the user payload. At the same
> time, tez AM logs a readable json file into the tez AM logs but only in DEBUG
> level. I'm proposing that tez.generate.debug.artifacts could write this
> readable json into a separated dag json file, this way:
> 1. we can use tez.generate.debug.artifacts to create one more useful file
> 2. don't have to set AM log level to DEBUG if we're only interested in the
> dag plan
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
