[
https://issues.apache.org/jira/browse/YARN-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267883#comment-14267883
]
Chris K Wensel commented on YARN-3009:
--------------------------------------
First, it's a little odd to put a value in quotes that is part of a query
string. but that's a reasonable workaround though non-obvious.
Second, this then becomes a bug in Apache Tez DAGClientTimelineImpl since it
does not quote values as it builds the query string.
fwiw, using quotes to prevent interpreting 77777 as a number instead of a
string makes a lot of sense. but quoting 7ABDCEFG to make sure it isn't
interpreted as a 7 is again non-intuitive.
> 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)
