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

Zhijie Shen commented on YARN-3625:
-----------------------------------

Hi, Jonathan! Would you mind give me an example to help understanding why the 
entity exists but the entity's domain is missing?

BTW, there's a special logic for LeveldbTimelineStore, where domain is 
implemented after the first version of store is done. So we need to to be 
compatible with the existing db data, which doesn't have domain. For 
RollingLevelDBTimelineStore, this shouldn't be a problem, right? We don't need 
the special treatment as well as the test case for it.

> 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)

Reply via email to