[
https://issues.apache.org/jira/browse/YARN-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-2818:
--
Attachment: YARN-2818.1.patch
Put a patch to remove this logic. The change should be mostly compatible. 2.6
server can still read the data created by 2.5, but take the owner as the normal
primary filter. 2.5 server can also read the 2.6 data. The only drawback is
that no owner info is available for entity-level acl control. However, as I've
mentioned in description, the owner info will be incomplete. So anyway, there's
a bug.
> Remove the logic to inject entity owner as the primary filter
> -
>
> Key: YARN-2818
> URL: https://issues.apache.org/jira/browse/YARN-2818
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Zhijie Shen
>Assignee: Zhijie Shen
>Priority: Critical
> Attachments: YARN-2818.1.patch
>
>
> In 2.5, we inject owner info as a primary filter to support entity-level
> acls. Since 2.6, we have a different acls solution (YARN-2102). Therefore,
> there's no need to inject owner info. There're two motivations:
> 1. For leveldb timeline store, the primary filter is expensive. When we have
> a primary filter, we need to make a complete copy of the entity on the logic
> index table.
> 2. Owner info is incomplete. Say we want to put E1 (owner = "tester",
> relatedEntity = "E2"). If E2 doesn't exist before, leveldb timeline store
> will create an empty E2 without owner info (at the db point of view, it
> doesn't know owner is a "special" primary filter).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
