[
https://issues.apache.org/jira/browse/YARN-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839198#comment-13839198
]
Karthik Kambatla commented on YARN-1399:
----------------------------------------
bq. And IMHO, the cheapest way may be converting the string to one case when
accepting it
Agree. Can store it internally in lowercase, and add documentation that the
filtering is not case-sensitive.
bq. I've no immediate idea about what the harm will be, and reasonable users
will seldom use these special chars. However, this constraint is what I feel
when I write the tags for my online album, bookmarks and etc. One possible
problem I can foresee is that users can write "<h1>MapReduce</h1>" to force the
display on the web page.
I am tempted to accept all unicode strings to begin with, and add restrictions
if we really need them. In this particular case of <h1>MapReduce</h1>, I think
we should show the user what he wants to see - it might not look good or
consistent with rest of the page, but that is what the user wanted. No?
> 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#6144)
