hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3009) TimelineWebServices always parses primary and secondary filters as numbers if first char is a number
Date Mon, 12 Jan 2015 17:51:35 GMT

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

Zhijie Shen commented on YARN-3009:
-----------------------------------

bq. but I suspect this is better served instead of key=nested_object as path/to/attribute=literal_value
(or a composition of them) query.

Would you please give an example about "path/to/attribute=literal_value"?

Filter are allows to be the nested JSON content, though usually people doesn't use it in this
fashion. IAC, we still chose to accept an object to be generalized. For example, the value
of primary filter could be a composite: {{primaryFilter=name:\{"first name":"Chris", "last
name" ="Wensel"\}.}}

Personally, I'm a bit reluctant to modifying the behavior of translating the value to a JSON
object, because it may break the compatibility to the existing Timeline API users. On the
other side, we have the walk around to force the interpreter to treat the value as a 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.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
(v6.3.4#6332)

Mime
View raw message