You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2016/04/18 16:19:25 UTC

[jira] [Commented] (SQOOP-2909) Oracle related ImportTest fails after SQOOP-2737

    [ https://issues.apache.org/jira/browse/SQOOP-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245734#comment-15245734 ] 

Jarek Jarcec Cecho commented on SQOOP-2909:
-------------------------------------------

Can you please follow the process and upload the patch to [review board|https://reviews.apache.org/dashboard/] [~maugli]?

> Oracle related ImportTest fails after SQOOP-2737
> ------------------------------------------------
>
>                 Key: SQOOP-2909
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2909
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Attila Szabo
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.4.7
>
>         Attachments: SQOOP-2909.patch
>
>
> After SQOOP-2737 had been implemented, Oracle ImportTest started to fail.
> SOOP-2737 aimed to support special characters (like whitespaces) in the name of the Oracle tables and columns. However the implementation works perfectly, the related test cases had not been changed, and as after escaping+quoting the underlying names become case sensitive, the whole ImporTest test suite started to fail



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