Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-2266

Sqoop2: Solution of communication between client and server about ErrorCode

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.99.5
    • Fix Version/s: 2.0.0
    • Component/s: sqoop2-client
    • Labels:
      None

      Description

      When the client receives the response with throwable bean from the server, it will try to reflect the exception class. However, if the ErrorCode class is in sqoop-core or other module instead of sqoop-common, NPE will be throw (SQOOP-2054). So Abraham Elmahrek and me moved all ErrorCode to sqoop-core (SQOOP-2054, SQOOP-2172). Several time passed, on the other hand, Jarek Jarcec Cecho fixed NPE with avoid throwing exception (SQOOP-2225), and then moved several ErrorCode back to their own modules (SQOOP-2248, SQOOP-2249, SQOOP-2251 and SQOOP-2247). But this solution does not solve the problem that client could not reflect the exception class from server, which is needed in Authorization part. (The client need to identify the exception type to decide which message should be shown in the CLI).
      This JIRA is to address this issue.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              richard_zhou Richard

              Dates

              • Created:
                Updated:

                Issue deployment