hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1399) Allow users to annotate an application with multiple tags
Date Fri, 03 Jan 2014 03:17:54 GMT

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

Vinod Kumar Vavilapalli commented on YARN-1399:
-----------------------------------------------

Agree that oozie should NOT kill apps as privileged user in any case.

bq. I am open to enforcing specifying either a user/queue when searching for a tag. However,
in principle, this could happen with application-types as well: a user could submit a number
of random YARN applications with type MAPREDUCE. I thought the way we were restricting exposing
these (tags/types) was through ACLs on a secure cluster.
Agreed about application-types too but two wrong things don't make a ... But I see your reasoning.
Solving this faking of application-types is hard.

I think that it boils down to
 - Documenting very clearly that types and tags can clash with other user's inputs and so
need to be judiciously used.
 - Having options when listing apps filtered by application-type or by application-tags (app-type
is a specific kind of tag, so clearly the later subsumes the former). The important bit is
that the default option be as restrictive as possible.

Today getApplications() API returns the list of ALL applications whether accessible or not.
That's a bad default that I thought I filed a ticket about. By default we should only return
the apps of the current user. Then there should be options to list all accessible apps (apps
with view-acl), and then finally all apps across all users. We could follow something similar
for this JIRA and set it as a precedent for fixing other existing issues with the default
listing and the listing against app-types?

May be we should punt on the last one (listing ALL apps) altogether so that user's can only
obtain lists of apps that they have access to. This does break the existing getApplications()
API which we can leave as is - in any case, information about all the apps that are not accessible
is completely blacked out, so it just serves as a simple listing.

> Allow users to annotate an application with multiple tags
> ---------------------------------------------------------
>
>                 Key: YARN-1399
>                 URL: https://issues.apache.org/jira/browse/YARN-1399
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>
> Nowadays, when submitting an application, users can fill the applicationType field to
facilitate searching it later. IMHO, it's good to accept multiple tags to allow users to describe
their applications in multiple aspects, including the application type. Then, searching by
tags may be more efficient for users to reach their desired application collection. It's pretty
much like the tag system of online photo/video/music and etc.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message