Vrushali C commented on YARN-4238:

The hbase cell timestamps may not indicate the actual entity modification time. 
They indicate the time at which that cell was written to hbase. For metrics, 
the cell timestamp is the event metric timestamp so that metrics can be 
arranged in chronological order in hbase. 

For timeline entities, I believe we should have a complete sync between the 
object model in code and the data model in hbase. So we either keep modified 
time in the entity class as well as in hbase as a column or remove it 

If we decide to keep modified time as a class member, could we have the 
timeline entity constructor populate it in the constructor as well as the 
client update it? Also how about we make all the setter methods in the entity 
class update the modified time value? That way the field value still stays 

> createdTime and modifiedTime is not reported while publishing entities to 
> ATSv2
> -------------------------------------------------------------------------------
>                 Key: YARN-4238
>                 URL: https://issues.apache.org/jira/browse/YARN-4238
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>              Labels: yarn-2928-1st-milestone
>         Attachments: YARN-4238-YARN-2928.01.patch, 
> YARN-4238-feature-YARN-2928.002.patch, YARN-4238-feature-YARN-2928.003.patch, 
> YARN-4238-feature-YARN-2928.02.patch
> While publishing entities from RM and elsewhere we are not sending created 
> time. For instance, created time in TimelineServiceV2Publisher class and for 
> other entities in other such similar classes is not updated. We can easily 
> update created time when sending application created event. Likewise for 
> modification time on every write.

This message was sent by Atlassian JIRA

Reply via email to