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-3074) Fix Avro import not to fail with Javac errors in case of non UTF-8 locale
Date Fri, 16 Dec 2016 10:50:58 GMT

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

ASF subversion and git services commented on SQOOP-3074:

Commit be30a344ee28ae60fcce9e9e45a0ec73c93209a7 in sqoop's branch refs/heads/trunk from [~maugli]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=be30a34 ]

SQOOP-3075: Simplify Unicode character support in
source files (introduced by SQOOP-3074) by
defining explicit locales instead of using

(Attila Szabo)

> Fix Avro import not to fail with Javac errors in case of non UTF-8 locale
> -------------------------------------------------------------------------
>                 Key: SQOOP-3074
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3074
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Attila Szabo
>            Assignee: Attila Szabo
>         Attachments: SQOOP-3074.patch
> The current implementation of Sqoop will fail to compile the ClassWriter generated Java
class in case of UTF-8 characters are available in the database  but the running host don't
have UTF-8 or not supporting that. 
> Meanwhile we'd like to keep up the support of UTF-8 characters for example in Avro schemas.
> A good example for that TestAvroImport#testNonstandardCharactersInColumnName fails if
executed form a shell/env with non UTF-8 locale.
> We have to provide an implementation reflects this.

This message was sent by Atlassian JIRA

View raw message