hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2445) ATS does not reflect changes to uploaded TimelineEntity
Date Sat, 23 Aug 2014 02:25:11 GMT

    [ https://issues.apache.org/jira/browse/YARN-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107808#comment-14107808

Billie Rinaldi commented on YARN-2445:

ATS is only designed to support aggregation.  In other words, each new primary filter or related
entity is added to what is already there for the entity.  You cannot remove previously put
information.  In this example, I would expect oldprop and newprop both to appear.

> ATS does not reflect changes to uploaded TimelineEntity
> -------------------------------------------------------
>                 Key: YARN-2445
>                 URL: https://issues.apache.org/jira/browse/YARN-2445
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelineserver
>            Reporter: Marcelo Vanzin
>            Priority: Minor
>         Attachments: ats2.java
> If you make a change to the TimelineEntity and send it to the ATS, that change is not
reflected in the stored data.
> For example, in the attached code, an existing primary filter is removed and a new one
is added. When you retrieve the entity from the ATS, it only contains the old value:
> {noformat}
> {"entities":[{"events":[],"entitytype":"test","entity":"testid-ad5380c0-090e-4982-8da8-21676fe4e9f4","starttime":1408746026958,"relatedentities":{},"primaryfilters":{"oldprop":["val"]},"otherinfo":{}}]}
> {noformat}
> Perhaps this is what the design wanted, but from an API user standpoint, it's really
confusing, since to upload events I have to upload the entity itself, and the changes are
not reflected.

This message was sent by Atlassian JIRA

View raw message