[
https://issues.apache.org/jira/browse/YARN-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470490#comment-16470490
]
Haibo Chen commented on YARN-7933:
----------------------------------
{quote} For storing in TimelineEntity, we should discuss it separately because
we are still not decided that should we store TimelineDomain as denormalized
form or just domain id in entity table
{quote}
In that case, probably we can remove the change to TimelineEntity.java and
leave it to the other jira.
{quote}Yes, it should be same as TimelineCollector context only.
TimelineV2Client#putDomain is still with in the scope of appId.
{quote}
Do you see any downside of removing appId from the query? If not, How about we
get rid of the appId param?
> [atsv2 read acls] Add TimelineWriter#writeDomain
> -------------------------------------------------
>
> Key: YARN-7933
> URL: https://issues.apache.org/jira/browse/YARN-7933
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Vrushali C
> Assignee: Rohith Sharma K S
> Priority: Major
> Attachments: YARN-7933.01.patch, YARN-7933.02.patch,
> YARN-7933.03.patch, YARN-7933.04.patch
>
>
>
> Add an API TimelineWriter#writeDomain for writing the domain info
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
