sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gwen Shapira (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2153) Sqoop2: Ensure creation of valid Avro schema names
Date Mon, 02 Mar 2015 02:15:04 GMT

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

Gwen Shapira commented on SQOOP-2153:
-------------------------------------

I'm +1, but can't commit due to authentication failures.

If someone can get to it first, feel free to go ahead :)

[~jarcec] Do you think its worthwhile to document how field names in Avro schema may be different
from source? Users may have apps that depend on those. I'm not sure how "internal" these names
are.

> Sqoop2: Ensure creation of valid Avro schema names
> --------------------------------------------------
>
>                 Key: SQOOP-2153
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2153
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.5
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.6
>
>         Attachments: SQOOP-2153.patch, SQOOP-2153.patch
>
>
> While creating integration tests for Kite connector, I've noticed that the connector
is directly using Schema names (both for schema itself and for all columns) as Avro names.
However we do not impose any restriction to the names wheres [Avro names are very strict|http://avro.apache.org/docs/1.7.7/spec.html#Names].
Hence if we are importing table that do not correspond to valid Avro name, we will error out
with quite confusing error message.



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

Mime
View raw message