[
https://issues.apache.org/jira/browse/SQOOP-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095265#comment-13095265
]
Jarek Jarcec Cecho edited comment on SQOOP-323 at 9/1/11 12:34 PM:
-------------------------------------------------------------------
Hi all,
this issue was pain in the neck for me because my task was to export several
tables from Microsoft SQL to hadoop/hive.
I've created patch that add support for NVARCHAR and NCHAR types to sqoop. It's
actually pretty simple - I've just added translations for this type to "String"
(both for java and hive).
I've tried that on several examples and I did not find any inconsistency.
However I'm not sure that there aren't needed any text transformations to
ensure that data are stored correctly.
I'm looking forward to any feedback.
Jarcec
was (Author: jarcec):
Hi all,
this issue was pain in the neck for me because my task was to export several
tables from Microsoft SQL to hadoop/hive.
I've created patch that add support for NVARCHAR and NCHAR types to sqoop. It's
actually pretty simple - I've just added translations for this type to
"String".
I've tried that on several examples and I did not find any inconsistency.
However I'm not sure that there aren't needed any text transformations to
ensure that data are stored correctly.
I'm looking forward to any feedback.
Jarcec
> Support for the NVARCHAR datatype
> ---------------------------------
>
> Key: SQOOP-323
> URL: https://issues.apache.org/jira/browse/SQOOP-323
> Project: Sqoop
> Issue Type: Bug
> Reporter: Kate Ting
> Attachments: SQOOP-323.patch
>
>
> Currently the presence of the NVARCHAR datatype results in an error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
