You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "PIERETTI ANTOINE (Commented) (JIRA)" <ji...@apache.org> on 2011/12/08 19:33:40 UTC
[jira] [Commented] (SQOOP-399) Sqoop import TIMESTAMP and DATE
differ between Avro and CSV imports
[ https://issues.apache.org/jira/browse/SQOOP-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165411#comment-13165411 ]
PIERETTI ANTOINE commented on SQOOP-399:
----------------------------------------
Hi,
another issue with the Avro DATE, TIMESTAMP representation as long, is when using oraoop, the value is represented by a String, so the check with the long type failed.
Regards.
Antoine
> Sqoop import TIMESTAMP and DATE differ between Avro and CSV imports
> -------------------------------------------------------------------
>
> Key: SQOOP-399
> URL: https://issues.apache.org/jira/browse/SQOOP-399
> Project: Sqoop
> Issue Type: Bug
> Reporter: Miki Tebeka
> Assignee: Jarek Jarcec Cecho
>
> When importing from PostgreSQL, TIMESTAMP and DATE columns are imported into long fields in Avro but into some kind of string representation in CSV import.
> Sqoop should be consistent and either use both epoch or string representation in both.
> (Also [here|https://issues.cloudera.org/browse/DISTRO-340]).
--
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