[jira] [Comment Edited] (YARN-5332) Jersey ClientResponse#getStatusInfo api is not available with jersey 1.9
[
https://issues.apache.org/jira/browse/YARN-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366130#comment-15366130
]
Tsuyoshi Ozawa edited comment on YARN-5332 at 7/7/16 1:51 PM:
--
[~sunilg] Thanks for reporting the issue. Please see [the doc of Jersey
1.19|https://jersey.java.net/apidocs/1.19/jersey/com/sun/jersey/api/client/ClientResponse.html#getClientResponseStatus()],
not one of 1.9 because we upgraded Jersey to 1.19. Feel free to ask me about
the update of dependency.
was (Author: ozawa):
[~sunilg] Thanks for reporting the issue. Please see [the doc of Jersey
1.19|https://jersey.java.net/apidocs/1.19/jersey/com/sun/jersey/api/client/ClientResponse.html#getClientResponseStatus()],
not 1.9 because we upgraded Jersey to 1.19. Feel free to ask me about the
update of dependency.
> Jersey ClientResponse#getStatusInfo api is not available with jersey 1.9
>
>
> Key: YARN-5332
> URL: https://issues.apache.org/jira/browse/YARN-5332
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Sunil G
>Assignee: Sunil G
>
> Few test classes like TestRMWebServices, were using
> ClientResponse#getStatusInfo and this api is not available as part of jersey
> 1.9.
> Pls refer:
> https://jersey.java.net/apidocs/1.9/jersey/com/sun/jersey/api/client/ClientResponse.html
> {{getStatusInfo}} is not present here.
> We may need to change such invocations from these test classes.
> In HADOOP-9613, [~ozawa] mentioned in this
> [comment|https://issues.apache.org/jira/browse/HADOOP-9613?focusedCommentId=14980024=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14980024]
> that we can use {{getStatusInfo}}.
> [~ozawa], could you please help to confirm this point Or am I missing some
> thing here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-5332) Jersey ClientResponse#getStatusInfo api is not available with jersey 1.9
[
https://issues.apache.org/jira/browse/YARN-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366130#comment-15366130
]
Tsuyoshi Ozawa edited comment on YARN-5332 at 7/7/16 1:50 PM:
--
[~sunilg] Thanks for reporting the issue. Please see [the doc of Jersey
1.19|https://jersey.java.net/apidocs/1.19/jersey/com/sun/jersey/api/client/ClientResponse.html#getClientResponseStatus()],
not 1.9 because we upgraded Jersey to 1.19. Feel free to ask me about the
update of dependency.
was (Author: ozawa):
[~sunilg] Thanks for reporting the issue. Please see the doc of Jersey 1.19,
not 1.9 because we upgraded Jersey to 1.19. Feel free to ask me about the
update of dependency.
https://jersey.java.net/apidocs/1.19/jersey/com/sun/jersey/api/client/ClientResponse.html#getClientResponseStatus()
> Jersey ClientResponse#getStatusInfo api is not available with jersey 1.9
>
>
> Key: YARN-5332
> URL: https://issues.apache.org/jira/browse/YARN-5332
> Project: Hadoop YARN
> Issue Type: Bug
> Components: test
>Reporter: Sunil G
>Assignee: Sunil G
>
> Few test classes like TestRMWebServices, were using
> ClientResponse#getStatusInfo and this api is not available as part of jersey
> 1.9.
> Pls refer:
> https://jersey.java.net/apidocs/1.9/jersey/com/sun/jersey/api/client/ClientResponse.html
> {{getStatusInfo}} is not present here.
> We may need to change such invocations from these test classes.
> In HADOOP-9613, [~ozawa] mentioned in this
> [comment|https://issues.apache.org/jira/browse/HADOOP-9613?focusedCommentId=14980024=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14980024]
> that we can use {{getStatusInfo}}.
> [~ozawa], could you please help to confirm this point Or am I missing some
> thing here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
