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 2015/02/25 03:01:05 UTC

[jira] [Updated] (SQOOP-2130) BaseSqoopTestCase should use manager.escapeTable instead of directly hardcoding double quotes

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

Jarek Jarcec Cecho updated SQOOP-2130:
--------------------------------------
    Attachment: SQOOP-2130.patch

> BaseSqoopTestCase should use manager.escapeTable instead of directly hardcoding double quotes
> ---------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-2130
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2130
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.6
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.4.6
>
>         Attachments: SQOOP-2130.patch
>
>
> I've changed {{BaseSqoopTestCase}} in SQOOP-1890 to hardcode escape character for table name to be double quotes per ANSI standard. Sadly this won't work with default MySQL configuration and breaks unless the server administrator sets {{sql_mode}} to {{ANSI_QUOTES}}. This seems unnecessary, so I would like to fix Sqoop instead to use the proper encoding character.



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