[
https://issues.apache.org/jira/browse/SQOOP-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230387#comment-13230387
]
Hudson commented on SQOOP-448:
------------------------------
Integrated in Sqoop-ant-jdk-1.6 #98 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6/98/])
SQOOP-448 boolean fields get nullified during postgres direct import into
hive.
(fix a problem in previous patch) (Revision 1301118)
Result = SUCCESS
blee : http://svn.apache.org/viewvc/?view=rev&rev=1301118
Files :
*
/incubator/sqoop/trunk/src/java/org/apache/sqoop/manager/DirectPostgresqlManager.java
> 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
> Assignee: Boris Partensky
> Labels: patch
> Fix For: 1.4.2-incubating
>
> Attachments: sqoop.patch, sqoop_diffs1.txt, sqoop_diffs2.txt
>
>
> 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
