[
https://issues.apache.org/jira/browse/TEZ-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695988#comment-14695988
]
Hitesh Shah commented on TEZ-2628:
----------------------------------
The timeline data was posted with both the Tez and YARN patches applied and
also retrieved via "/ws/v1/timeline/HIVE_QUERY_ID".
My current configs use something along these lines:
{code}
<property>
<name>yarn.timeline-service.store-class</name>
<value>org.apache.hadoop.yarn.server.timeline.EntityFileTimelineStore</value>
</property>
<property>
<name>yarn.timeline-service.entity-file-store.summary-entity-types</name>
<value>
TEZ_DAG_ID,TEZ_APPLICATION,TEZ_APPLICATION_ATTEMPT,HIVE_QUERY_ID,YARN_APPLICATION_ATTEMPT,YARN_APPLICATION</value>
</property>
{code}
> History logging plugin to write ATS events to HDFS
> --------------------------------------------------
>
> Key: TEZ-2628
> URL: https://issues.apache.org/jira/browse/TEZ-2628
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: TEZ-2628.001.patch, hive-timeline.json
>
>
> This provides another history logging alternative that conceptually the same
> as the timeline logging service but logs the entities to a file rather than
> posting the events to the timeline server directly. When coupled with the
> timeline store plugin from YARN-3942 it allows the Tez job to be decoupled
> from the timeline server yet the Tez UI can still function properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
