Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 7 Jan 2015 20:26:35 +0000 (UTC)
From: "Billie Rinaldi (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12765046.1420515474000.31180.1420662395189@Atlassian.JIRA>
In-Reply-To: <JIRA.12765046.1420515474000@Atlassian.JIRA>
References: <JIRA.12765046.1420515474000@Atlassian.JIRA>
 <JIRA.12765046.1420515474517@arcas>
Subject: [jira] [Commented] (YARN-3009) TimelineWebServices always parses
 primary and secondary filters as numbers if first char is a number
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Billie Rinaldi commented on YARN-3009:
--------------------------------------

bq. the nested Json structure will be mistaken as a string
Okay, would it be sufficient if we did not perform the comparison with the original String when the resulting Object is a List or Map?  Or do you think a different approach would be better?

> 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)