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] [Commented] (SQOOP-1073) Sqoop2: Introduce schema for transferred data
Date Tue, 25 Jun 2013 21:55:20 GMT

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

Jarek Jarcec Cecho commented on SQOOP-1073:
-------------------------------------------

For reviewers: For the convenience, I've uploaded entire big patch to review board and also
slice it into three more or less independent pieces for easier review. Please do finally commit
the patch here on SQOOP-1073, not the pieces in the sub tasks. However please comment whenever
you see fit, I'll be more than happy to incorporate comments from all reviews.
                
> 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: 1.99.3
>
>         Attachments: rb12092.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

Mime
View raw message