[
https://issues.apache.org/jira/browse/YARN-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268506#comment-14268506
]
Chris K Wensel commented on YARN-3009:
--------------------------------------
Feels as if the api is becoming conflated if the filter value could be a nested
JSON object instead of a literal value (string or number). Let alone brittle.
If this is a requirement of the api, I would expose a new parameter on the
query that clearly states the value should be interpreted as an object.
but I suspect this is better served instead of key=nested_object as
path/to/attribute=literal_value (or a composition of them) query.
> 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
>
>
> 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)
