[
https://issues.apache.org/jira/browse/SQOOP-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289886#comment-15289886
]
Hudson commented on SQOOP-2863:
-------------------------------
FAILURE: Integrated in Sqoop-hadoop20 #1050 (See
[https://builds.apache.org/job/Sqoop-hadoop20/1050/])
SQOOP-2911: Fix failing HCatalogExportTest caused by SQOOP-2863 (jarcec:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=83f0c1a40b96d7aab8262fae527066770dba097d])
* src/test/com/cloudera/sqoop/testutil/ExportJobTestCase.java
* src/test/com/cloudera/sqoop/TestExport.java
> Properly escape column names for generated INSERT statements
> ------------------------------------------------------------
>
> Key: SQOOP-2863
> URL: https://issues.apache.org/jira/browse/SQOOP-2863
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.6
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.4.7
>
> Attachments: SQOOP-2863.patch
>
>
> I had a user who reported issue with invalid queries being generated during
> export operation. The export table had various unusual column names. We've
> significantly improved our behavior with properly escaping table/column names
> for import part in SQOOP-1890, but it seems that we did not do that for
> export.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
