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 22:30:27 UTC

[jira] [Resolved] (SQOOP-2008) Matching rules between from / to schema -revisted ( Use the avro model)

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

Jarek Jarcec Cecho resolved SQOOP-2008.
---------------------------------------
    Resolution: Fixed

The IDF framework isn't place to do schema evolution (it's just data exchange), so I'll resolve this JIRA for now.

> Matching rules between from / to schema -revisted ( Use the avro model)
> -----------------------------------------------------------------------
>
>                 Key: SQOOP-2008
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2008
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>             Fix For: 2.0.0
>
>
> Is it a norm to fill unmatched columns with nulls as we do ?
> {code}
>   protected void tryFillNullInArrayForUnexpectedColumn(Column column,
>       Object[] array, int index) throws SqoopException {
>     if (!column.isNullable()) {
>       throw new SqoopException(SchemaError.SCHEMA_0004, "Target column " +
>           column + " didn't match with any source column and cannot be null.");
>     }
>     LOG.warn("Column " + column +
>         " has no matching source column. Will be ignored.");
>     array[index] = null;
>   }
> {code}
> I looked at kites schema resolution is neat
> http://kitesdk.org/docs/0.17.1/Schema-Evolution.html 
> similar concepts can be applied in sqoop and it relies on of how avro does reader/ writer schema resolution 



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