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 2012/10/12 19:15:02 UTC
[jira] [Commented] (SQOOP-628) Postgres direct import fails on
non-lowercase column names
[ https://issues.apache.org/jira/browse/SQOOP-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475170#comment-13475170 ]
Jarek Jarcec Cecho commented on SQOOP-628:
------------------------------------------
Hi Paul,
thank you very much for your contribution. Would you mind uploading your patch to Apache review board (https://reviews.apache.org) so that we can further review it?
> Postgres direct import fails on non-lowercase column names
> ----------------------------------------------------------
>
> Key: SQOOP-628
> URL: https://issues.apache.org/jira/browse/SQOOP-628
> Project: Sqoop
> Issue Type: Bug
> Components: connectors/postgresql
> Affects Versions: 1.4.2
> Reporter: Paul Butler
> Attachments: postgres-direct-column-case.patch
>
>
> Postgresql requires non-lowercase column names to be escaped. Sqoop currently does this for the JDBC client but does not for the direct import.
> I've attached a patch that brings column escaping from the JDBC side to the direct import.
--
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