[
https://issues.apache.org/jira/browse/TEZ-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276062#comment-17276062
]
László Bodor edited comment on TEZ-4039 at 2/1/21, 5:36 AM:
------------------------------------------------------------
[~prasanth_j], [~jeagles]: is there a chance that we can refresh this one? I
remember I left this here in a fully working state
now I created a PR on top of master: https://github.com/apache/tez/pull/98/
testing steps are above, but instead of 05.patch, it's recommended to use the
latest revision from the [tree|https://github.com/abstractdog/tez/tree/TEZ-4039]
was (Author: abstractdog):
[~prasanth_j], [~jeagles]: is there a chance that we can refresh this one? I
remember I left this here in a fully working state
now I created a PR on top of master: https://github.com/apache/tez/pull/98/
> Tez should inject dag id, query id into MDC
> -------------------------------------------
>
> Key: TEZ-4039
> URL: https://issues.apache.org/jira/browse/TEZ-4039
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Prasanth Jayachandran
> Assignee: László Bodor
> Priority: Major
> Attachments: TEZ-4039.01.patch, TEZ-4039.02.patch, TEZ-4039.03.patch,
> TEZ-4039.04.patch, TEZ-4039.05.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Tez currently uses CallableWithNdc to store thread specific context. It
> should also inject the context into MDC so that pattern layout can dump the
> contexts from MDC (with NDC it is not possible to read the context in pattern
> lyaout).
> Hive for example, sets queryId in the MDC and pattern layout prints the
> queryId
>
> {code:java}
> %d{ISO8601} %-5p [%t (%X{queryId})] %c{2}: %m%n
> {code}
> Llap sets dagId, fragmentId and queryId into MDC which is used for queryId
> based routing of logging.
> Similarly, Tez AM should set dagId and queryId (if available) into MDC.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
