Jarek Jarcec Cecho created SQOOP-2546:
-----------------------------------------
Summary: Sqoop2: RESTiliency: Unify behavior on getting details on
non-existing connector
Key: SQOOP-2546
URL: https://issues.apache.org/jira/browse/SQOOP-2546
Project: Sqoop
Issue Type: Sub-task
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 1.99.7
Here is test code that is testing our behavior on non existing connector:
{code}
new TestDescription("Get connector by non-existing ID", "v1/connector/666",
"GET", null, new Validator() {
@Override
void validate() throws Exception {
assertResponseCode(500);
assertServerException("org.apache.sqoop.error.code.CommonRepositoryError",
"COMMON_0057");
}}),
new TestDescription("Get connector by non-existing name",
"v1/connector/jarcecs-cool-connector", "GET", null, new Validator() {
@Override
void validate() throws Exception {
assertResponseCode(500);
assertServerException("org.apache.sqoop.server.common.ServerError",
"SERVER_0005");
}}),
{code}
Depending whether one asks for non-existing connector ID or non-existing
connector name, he gets different answer. That seems really weird for single
REST end point and I think that we should fix that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
