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

Rohith Sharma K S commented on YARN-7986:
-----------------------------------------

Thanks [~charanh] for reporting this issue. This seems to be an issue with tags 
which is sent in ApplicationSubmissionContext. I see 
ApplicationSubmissionContextPBImpl sets explicitly to lowercase. Seems like 
tags are case insensitive as we see explicit comment in below code.
{code}
@Override
  public void setApplicationTags(Set<String> tags) {
     ...
     ...
    // Convert applicationTags to lower case and add
    this.applicationTags = new HashSet<String>();
    for (String tag : tags) {
      this.applicationTags.add(StringUtils.toLowerCase(tag));
    }
  }
{code}

ATSv2 is designed to be case sensitive. So either we might need to add 
documentation that providing a tags is always case insensitive or ATSv2 code 
always convert all the parameter into lowercase and store it in back end. 
[~vrushalic] [~haibo.chen] any suggestions on this ?  

> ATSv2 REST API queries do not return results for uppercase application tags
> ---------------------------------------------------------------------------
>
>                 Key: YARN-7986
>                 URL: https://issues.apache.org/jira/browse/YARN-7986
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Charan Hebri
>            Priority: Critical
>
> When applications are submitted to YARN with application tags, the tags are 
> converted to lowercase. This can be seen on the old/new UI. But using the 
> original tags for ATSv2 REST API queries do not return results as they expect 
> the query url to have the tagsĀ in lowercase. 
> This is additional work for the client because each tag needs to be 
> lowercased before running a query.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to