Zhijie Shen commented on YARN-2446:

bq. It seems like the recommended approach is for users to set the namespace id 
on each entity when they do a post? Would it help to support an api to set a 
current namespace id on the client and fall back to using it if the entity does 
not have a namespace id specified?

That's right. And the designed behavior is that when user forget to specify a 
domain, it will automatically fall into a default domain that allows everybody 
to access.

bq.  would like to confirm that it is fine to set the owner of default 
namespace to current user. Since this is a lazy initialization, the owner of 
the default namespace is not deterministic. Will this cause any troubles in 

The current user here should the user who starts the timeline server, and it's 
going to be the owner of the default user. It should cause trouble, but 
timeline server started by user1 can load a default domain created by user2, 
but it doesn't matter as it is an open space for everybody. Add a code comment 

bq. Is it possible to have a scenario where the user is not changing the 
namespace, but just set it wrong? If this scenario is possible, maybe we want 
to change the exception message since it may be a little bit confusing.

It's possible, but we cannot identify user intentionally sets a different 
domain or by mistake. The result is that the user will try to change the domain 
of an existing entity, and is rejected.

bq. Maybe we want to change the name of this function?

Name updated

The new patch also rebases against latest YARN-2102 patch.

> Using TimelineNamespace to shield the entities of a user
> --------------------------------------------------------
>                 Key: YARN-2446
>                 URL: https://issues.apache.org/jira/browse/YARN-2446
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>         Attachments: YARN-2446.1.patch
> Given YARN-2102 adds TimelineNamespace, we can make use of it to shield the 
> entities, preventing them from being accessed or affected by other users' 
> operations.

This message was sent by Atlassian JIRA

Reply via email to