sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1073) Sqoop2: Introduce schema for transferred data
Date Tue, 25 Jun 2013 21:37:20 GMT

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

Jarek Jarcec Cecho updated SQOOP-1073:

    Attachment: bugSQOOP-1073.patch

Attached referenced patch is the entire implementation. It has 90Kb, so I'll split it up into
sub tasks for easier review.
> Sqoop2: Introduce schema for transferred data
> ---------------------------------------------
>                 Key: SQOOP-1073
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1073
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.99.2
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 2.0.0
>         Attachments: bugSQOOP-1073.patch
> Sqoop2 similarly as Sqoop1 is not keeping schema of transferred data. As we are planning
to modularize entire framework, I believe that schema should be generated and provided to
all moving pieces (like {{extractor}}, {{loader}}, ...).

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

View raw message