[
https://issues.apache.org/jira/browse/SQOOP-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124472#comment-13124472
]
Chris Tierney commented on SQOOP-358:
-------------------------------------
Oh whoops, I was thinking that the case statements that were edited in
SQOOP-323 were doing the same thing, but they are not.
> Sqoop import fails on netezza nvarchar datatype with --as-avrodatafile
> ----------------------------------------------------------------------
>
> Key: SQOOP-358
> URL: https://issues.apache.org/jira/browse/SQOOP-358
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Chris Tierney
> Labels: netezza
> Fix For: 1.4.0
>
> Attachments: SQOOP-358.patch
>
>
> Using --as-avrodatafile causes sqoop to error on nvarchar fields as well as
> presumably longnvarchars. This is the same bug as SQOOP-323 except with the
> avro export turned on.
--
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
