[
https://issues.apache.org/jira/browse/YARN-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267909#comment-14267909
]
Billie Rinaldi commented on YARN-3009:
--------------------------------------
bq. but quoting 7ABDCEFG to make sure it isn't interpreted as a 7 is again
non-intuitive
It's a good point, and I was also confused by this recently. After converting
the filter String to an Object, we could check that the Object can be converted
back into the correct String, and if it can't, fall back to using the String.
> 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.4.0
> Reporter: Chris K Wensel
> Assignee: Naganarasimha G R
>
> 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
(v6.3.4#6332)
