[SQOOP-2266] Sqoop2: Solution of communication between client and server about ErrorCode

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.99.5
• Fix Version/s: 2.0.0
• Component/s: sqoop2-client
• Assignee: Unassigned
• Reporter: Richard
• Created: 25/Mar/15 07:20
• Updated: 25/Mar/15 14:49

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 abec and me moved all ErrorCode to sqoop-core (SQOOP-2054, SQOOP-2172). Several time passed, on the other hand, jarcec 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.

Issue Links

• relates to: SQOOP-2248 Sqoop2: ErrorCodes: Move ServerError to server module
• relates to: SQOOP-2249 Sqoop2: ErrorCodes: Move SecurityError to core module
• relates to: SQOOP-2251 Sqoop2: ErrorCodes: Move RepositoryError to core module
• relates to: SQOOP-2247 Sqoop2: Move error code classes back to their modules
• relates to: SQOOP-2054 Sqoop2: Client cannot understand server exceptions
• relates to: SQOOP-2172 Sqoop2: Move ErrorCode's sub-class from sqoop-core to sqoop-common
• relates to: SQOOP-2225 Sqoop2: Shell client clobbers server exceptions