sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shuaishuai Nie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1030) Enable column types Binary and Varbinary parsing in Sqoop for export
Date Wed, 22 May 2013 18:15:22 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shuaishuai Nie updated SQOOP-1030:
----------------------------------

    Attachment: SQOOP-1030.3.patch

Thanks for the advice [~jarcec]. Added the row content check in the test
                
> Enable column types Binary and Varbinary parsing in Sqoop for export
> --------------------------------------------------------------------
>
>                 Key: SQOOP-1030
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1030
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.4
>            Reporter: Shuaishuai Nie
>            Assignee: Shuaishuai Nie
>              Labels: codegen
>         Attachments: SQOOP-1030.1.patch, SQOOP-1030.2.patch, SQOOP-1030.3.patch
>
>
> Enable parsing Binary and Varbinary column types which are represented as BytesWritable
in Sqoop generated classes. Currently, Sqoop generated classes for database tables support
serializing BytesWritable fields into files (while importing), but not the other way around
for deserializing the records back when exporting from HDFS.
>  We need to handle this for supporting Varbinary federation columns as well as Binary
and Varbinary columns in 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