[
https://issues.apache.org/jira/browse/YARN-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859053#comment-13859053
]
Robert Kanter commented on YARN-1399:
-------------------------------------
{quote}
Having GUID in the workflow ID to prevent conflicting IDs in a YARN cluster
(unless others intentionally attack)
{quote}
Oozie workflow ID's are configurable, but by default they are
{{<job_number>\-<timesteamp>\-<system_id>-<job_type>}}. These should be unique
so we don't need a separate GUID. We'd actually use the action ID instead of
the workflow ID, but that's just {{<workflow_ID>@<action_name>}}, which is also
unique. For example: {{0000005-131218150050953-oozie-oozi-W@pig-node}}
Unless the user configured multiple Oozie servers such that the IDs would be
similar, the only way to get the same workflow or action id would be to start
the two servers at exactly the same time so they'd have the same timestamp,
which I don't think we need to worry about.
> 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)
