[jira] [Updated] (YARN-3009) TimelineWebServices always parses primary and secondary filters as numbers if first char is a number
[
https://issues.apache.org/jira/browse/YARN-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naganarasimha G R updated YARN-3009:
Attachment: YARN-3009.20150111-1.patch
Hi [~zjshen],[~billie.rinaldi] [~cwensel]
I am uploading a patch with the approach which i had mentioned {{if the
resulting object is subclass of java.lang.Number, then we can have the check
which i have given earlier}}.
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)
[jira] [Updated] (YARN-3009) TimelineWebServices always parses primary and secondary filters as numbers if first char is a number
[ https://issues.apache.org/jira/browse/YARN-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3009: Attachment: YARN-3009.20150108-1.patch Attaching the patch 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)
