Naganarasimha G R commented on YARN-3009:

Hi [~cwensel]
Took a look @ code and test cases. Seems like its not a issue, if the filter 
value is placed within double quotes then its expected to be read as a string, 
if not it will read as numerical object itself (refer 
{{TestTimelineWebServices.testPrimaryFilterNumericString() && 
testPrimaryFilterNumericStringWithQuotes()}} )
May be you can share the URL which you are using to store and accessing the 
timeline entities through webservice, which can help in validating this issue 

> 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

Reply via email to