[
https://issues.apache.org/jira/browse/SQOOP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662883#comment-13662883
]
Hudson commented on SQOOP-1031:
-------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop100 #638 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop100/638/])
SQOOP-1031: Provide default Java type mapping for MS Sql Datetimeoffset
type (Revision 28af5122ea8778b5fcd6341a492d64283c706b08)
Result = SUCCESS
jarcec :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=28af5122ea8778b5fcd6341a492d64283c706b08
Files :
* src/java/org/apache/sqoop/manager/SQLServerManager.java
> 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
> Fix For: 1.4.4
>
> 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
