You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Scott Vallely (JIRA)" <ji...@apache.org> on 2014/04/17 19:07:14 UTC
[jira] [Updated] (SQOOP-1311) Postgres JDBC/direct driver dropping
microseconds from 'time without timezone' fields
[ https://issues.apache.org/jira/browse/SQOOP-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Vallely updated SQOOP-1311:
---------------------------------
Summary: Postgres JDBC/direct driver dropping microseconds from 'time without timezone' fields (was: Postgres JDBC/direct driver (not direct connect) dropping microseconds from 'time without timezone' fields)
> Postgres JDBC/direct driver dropping microseconds from 'time without timezone' fields
> -------------------------------------------------------------------------------------
>
> Key: SQOOP-1311
> URL: https://issues.apache.org/jira/browse/SQOOP-1311
> Project: Sqoop
> Issue Type: Bug
> Components: connectors/postgresql, sqoop2-client
> Affects Versions: 1.4.3
> Environment: CDH 4.6, Postgres JDBC/direct drivers
> Reporter: Scott Vallely
>
> When Sqoop importing from Postgres, with both the direct and generic JDBC drivers, a field of type 'time without timezone' gets its microseconds dropped.
> Example.
> Data in Postgres:
> 142
> 318
> 2
> 2012-10-04
> null
> 2014-04-09 05:30:00-04
> null
> null
> 31
> 2014-04-08 05:30:00-04
> 05:30:00.489898
> Data in HDFS (with unprintable field delimiters):
> 14231822012-10-04null2014-04-09 05:30:00.0nullnull312014-04-08 05:30:00.005:30:00
--
This message was sent by Atlassian JIRA
(v6.2#6252)