[
https://issues.apache.org/jira/browse/SQOOP-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702904#comment-13702904
]
Jarek Jarcec Cecho commented on SQOOP-1128:
-------------------------------------------
Thank you for pointing out the missing pre-commit build [~venkatnrangan]! It
was kicked off in build
[#45|https://builds.apache.org/job/PreCommit-SQOOP-Build/45/console] but failed
as it wasn't able to derive whether this patch is for branch {{trunk}} (Sqoop1)
or for sqoop2. The reason for that is that field {{affectedVersion}} was empty.
The Pre-Commit build is currently a bit conservative and it's dying silently
rather than spamming the JIRA. Maybe we can tweak it a bit if this will become
an issue.
> Sqoop2: SqoopException being nested into another SqoopException in Repository
> -----------------------------------------------------------------------------
>
> Key: SQOOP-1128
> URL: https://issues.apache.org/jira/browse/SQOOP-1128
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.2
> Reporter: Mengwei Ding
> Assignee: Mengwei Ding
> Fix For: 1.99.3
>
> Attachments: SQOOP-1128.1.patch
>
>
> In the upgradeConnector() and upgradeFramework() methods in Repository.java,
> the JDBCREPO_0027 SqoopException will be caught and wrapped into another
> SqoopException.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
