[
https://issues.apache.org/jira/browse/SQOOP-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547148#comment-13547148
]
Hudson commented on SQOOP-820:
------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop200 #483 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/483/])
SQOOP-820: Escape table name in export job only if it's required by
connector (Revision b02ddc39757771fb387c2688ccd0cee74cf6032c)
Result = SUCCESS
cheolsoo :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=b02ddc39757771fb387c2688ccd0cee74cf6032c
Files :
* src/java/org/apache/sqoop/mapreduce/JdbcExportJob.java
* src/java/org/apache/sqoop/manager/SQLServerManager.java
* src/java/org/apache/sqoop/manager/PostgresqlManager.java
* src/java/org/apache/sqoop/manager/ConnManager.java
> Escape table name in export job only if it's required by connector
> ------------------------------------------------------------------
>
> Key: SQOOP-820
> URL: https://issues.apache.org/jira/browse/SQOOP-820
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Priority: Blocker
> Fix For: 1.4.3
>
> Attachments: SQOOP-820.patch
>
>
> During investigation on SQOOP-818 I've noticed that automatically escaping
> table name when saving to mapreduce configuration introduced in SQOOP-601
> might cause issues to third party connectors that are expecting that the name
> won't be ever escaped.
--
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
