sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boris Partensky (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-448) boolean fields get nullified during postgres direct import into hive.
Date Wed, 29 Feb 2012 12:49:57 GMT

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

Boris Partensky updated SQOOP-448:

    Attachment: sqoop.patch

diffs for the fix
> boolean fields get nullified during postgres direct import into hive.
> ---------------------------------------------------------------------
>                 Key: SQOOP-448
>                 URL: https://issues.apache.org/jira/browse/SQOOP-448
>             Project: Sqoop
>          Issue Type: Bug
>          Components: connectors/postgresql
>    Affects Versions: 1.3.0
>            Reporter: Boris Partensky
>              Labels: patch
>             Fix For: 1.3.0
>         Attachments: sqoop.patch
> These diffs address this issue - https://issues.cloudera.org/browse/SQOOP-43.
> I changed DirectPostgresManager.java to special-case rewrite COPY.... command for boolean
fields so that hive sees "true"/"false". The only shortcoming with my patch is that because
PG jdbc driver can not tell bit data types from booleans, direct import will break with SQL
cast errors if someone has real bit fields. Not sure how often people use those, but it will
break direct import for that one person who does. If you have an idea on how I can make this
better, let me know. Diffs are attached

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message