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-1729) TimelineWebServices always passes primary and secondary filters as strings
Date Mon, 03 Mar 2014 19:50:21 GMT

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

Zhijie Shen commented on YARN-1729:

1. mapper is not necessary, objectReader and objectReader should be final, and both constants
can be initiated in a static block. And please follow the name convention of the static final
+  private static ObjectMapper mapper = new ObjectMapper();
+  private static ObjectReader objectReader = mapper.reader(Object.class);
+  private static ObjectWriter objectWriter = mapper.writer();

2. Similar problem here.
+  private static ObjectReader objectReader =
+      new ObjectMapper().reader(Object.class);

3. In the test case, would you mind adding one more test case of "other:123abc" to show the
+    ClientResponse response = r.path("ws").path("v1").path("timeline")
+        .path("type_1").queryParam("primaryFilter", "other:\"123abc\"")

Other than that, the patch looks good to me.

In addition, I'm aware of an additional issue of the leveldb implementation, which is aware
of JSON input specification. This means whenever our RESTful APIs allows to take XML input,
the current implementation may not work correctly. IMHO, ideally the store should be isolated
from the RESTful interface input types. Anyway, let's leave the issue separately not to block
this patch, as the issue happens before this patch as well.

> TimelineWebServices always passes primary and secondary filters as strings
> --------------------------------------------------------------------------
>                 Key: YARN-1729
>                 URL: https://issues.apache.org/jira/browse/YARN-1729
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>         Attachments: YARN-1729.1.patch, YARN-1729.2.patch, YARN-1729.3.patch, YARN-1729.4.patch,
> Primary filters and secondary filter values can be arbitrary json-compatible Object.
 The web services should determine if the filters specified as query parameters are objects
or strings before passing them to the store.

This message was sent by Atlassian JIRA

View raw message