sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1073) Sqoop2: Introduce schema for transferred data
Date Mon, 01 Jul 2013 04:07:20 GMT

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

ASF subversion and git services commented on SQOOP-1073:

Commit aa8e1e77945cc4ae07549e70d4d481f974a24724 in branch refs/heads/sqoop2 from [~venkatnrangan]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=aa8e1e7 ]

SQOOP-1073: Sqoop2: Introduce schema for transferred data

 (Jarek Jarcec Cecho via Venkat Ranganathan)

> 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: bugSQOOP-1073.patch, 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