You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2015/10/21 03:19:27 UTC

[jira] [Resolved] (SQOOP-1074) Sqoop2: Allow mapping between source and target schema

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

Jarek Jarcec Cecho resolved SQOOP-1074.
---------------------------------------
    Resolution: Not A Problem

We already have notion of {{Matcher}} that enables schema mapping in the sense that I was thinking about when filing this JIRA.

> Sqoop2: Allow mapping between source and target schema
> ------------------------------------------------------
>
>                 Key: SQOOP-1074
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1074
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.99.2
>            Reporter: Jarek Jarcec Cecho
>             Fix For: 2.0.0
>
>
> Sqoop2 similarly as Sqoop2 currently do not allows any schema mapping between source and target system. It's assumed that target schema (e.g. {{SequenceFile}}, or table in Hive) is exactly the same as the table in source database. I think that we should allow some level of mapping there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)