sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bilung Lee (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-358) Sqoop import fails on netezza nvarchar datatype with --as-avrodatafile
Date Sat, 08 Oct 2011 05:01:30 GMT

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

Bilung Lee commented on SQOOP-358:

Thanks for contributing, Chris! Yes, in general it would be nice to consolidate repeating
code into a utility class.  What are the other places you are referring to though?

> 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


View raw message