sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1031) Provide default Java type mapping for MS Sql Datetimeoffset type
Date Tue, 21 May 2013 06:25:16 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662738#comment-13662738
] 

Jarek Jarcec Cecho commented on SQOOP-1031:
-------------------------------------------

Thank you [~shuainie] for the explanation! I'm a bit concerned about what will happen when
the Java will adopt the value -155 for something else, but as that is more general issue outside
scope of Sqoop, I'm +1 on the patch.
                
> Provide default Java type mapping for MS Sql Datetimeoffset type
> ----------------------------------------------------------------
>
>                 Key: SQOOP-1031
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1031
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.4
>            Reporter: Shuaishuai Nie
>            Assignee: Shuaishuai Nie
>         Attachments: SQOOP-1031.1.patch
>
>
> MS SQL database type datetimeoffset causes errors when importing to HDFS. We need to
provide a default mapping in SQLServerManager which could still be overriden by users if wanted.
> In order to preserve time zone offset we use String instead of TimeStamp. This would
still work when exporting the imported data back to MS SQL Server

--
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

Mime
View raw message