[
https://issues.apache.org/jira/browse/SQOOP-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092318#comment-14092318
]
Sqoop QA bot commented on SQOOP-1426:
-------------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12660899/SQOOP-1426.patch
against branch sqoop2.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to apply patch (exit code 1):
{code}error: patch failed:
common/src/test/java/org/apache/sqoop/json/TestThrowableBean.java:17
error: common/src/test/java/org/apache/sqoop/json/TestThrowableBean.java: patch
does not apply
{code}
{color:green}SUCCESS:{color} Clean was successful
Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/295/console
This message is automatically generated.
> Sqoop2: ThrowableBean should correct reconstruct SqoopException
> ---------------------------------------------------------------
>
> Key: SQOOP-1426
> URL: https://issues.apache.org/jira/browse/SQOOP-1426
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.3
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.4
>
> Attachments: SQOOP-1426.patch
>
>
> {{ThrowableBean}} will currently always transform all {{SqoopException}}
> instances into generic {{Throwable}} as the generic way of re-creating the
> exceptions won't work. As the {{SqoopException}} is central Sqoop, I think
> that we should make the effort to reconstruct the original exception if
> possible.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
