[
https://issues.apache.org/jira/browse/YARN-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542582#comment-14542582
]
Zhijie Shen commented on YARN-3625:
-----------------------------------
bq. To handle this scenario, I relax the domain checking to mean if a domain is
non-existent we can treat this as if we are in the temporary state we have
staged the domain to be written for the related entity but have not yet written
it to the database.
I see. What to do with the following case if entity1 of domain1 relates to
entity2 of domain2, and they're put in a same batch? According to the patch, it
seems that the relation will be allowed, right? However, we previously stop the
relationship across domains.
> RollingLevelDBTimelineStore Incorrectly Forbids Related Entity in Same Put
> --------------------------------------------------------------------------
>
> Key: YARN-3625
> URL: https://issues.apache.org/jira/browse/YARN-3625
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: YARN-3625.1.patch, YARN-3625.2.patch
>
>
> RollingLevelDBTimelineStore batches all entities in the same put to improve
> performance. This causes an error when relating to an entity in the same put
> however.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
