[ 
https://issues.apache.org/jira/browse/SQOOP-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard updated SQOOP-2266:
---------------------------
    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.

  was:
When the client receives the response with throwable bean from the server, it 
will try to reflect the exception class. However, it 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}} into 
{{sqoop-core}} (SQOOP-2054, SQOOP-2172). And [~jarcec] fixed {{NPE}} with avoid 
throwing exception (SQOOP-2225), then moved several {{ErrorCode}} back to their 
own module (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.


> Sqoop2: Solution of communication between client and server about ErrorCode
> ---------------------------------------------------------------------------
>
>                 Key: SQOOP-2266
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2266
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-client
>    Affects Versions: 1.99.5
>            Reporter: Richard
>             Fix For: 2.0.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to