[SQOOP-2546] Sqoop2: RESTiliency: Unify behavior on getting details on non-existing connector

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.99.7
• Assignee: Colin
• Reporter: Jarek Jarcec Cecho
• Created: 29/Aug/15 13:44
• Updated: 24/Dec/15 12:09
• Resolved: 24/Dec/15 11:50

Description

Here is test code that is testing our behavior on non existing connector:

    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");
      }}),

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.

Issue Links

• links to: Review board