Zhijie Shen commented on YARN-3009:

[~Naganarasimha], thanks for the patch. I think your work around is going to 
mitigate the problem. However, my concern is whether we should do this work 
around instead of how to do it correctly. While I understand it's 
counter-intuitive to use (double) quotes to enforce the value as a string, I'm 
afraid *atoi* or *atof* of jackson parser is probably doing the right thing. A 
string that starts with numeric char, but contains non-numeric char could still 
be a valid number. For example,the value is {{123456D}} or {{123.45E+6}}. On 
the other side, we can also consider them as a string, e.g., representing an ID.

> TimelineWebServices always parses primary and secondary filters as numbers if 
> first char is a number
> ----------------------------------------------------------------------------------------------------
>                 Key: YARN-3009
>                 URL: https://issues.apache.org/jira/browse/YARN-3009
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelineserver
>    Affects Versions: 2.6.0
>            Reporter: Chris K Wensel
>            Assignee: Naganarasimha G R
>         Attachments: YARN-3009.20150108-1.patch, YARN-3009.20150111-1.patch
> If you pass a filter value that starts with a number (7CCA...), the filter 
> value will be parsed into the Number '7' causing the filter to fail the 
> search.
> Should be noted the actual value as stored via a PUT operation is properly 
> parsed and stored as a String.
> This manifests as a very hard to identify issue with DAGClient in Apache Tez 
> and naming dags/vertices with alphanumeric guid values.

This message was sent by Atlassian JIRA

Reply via email to