You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Attila Szabo (JIRA)" <ji...@apache.org> on 2016/12/08 18:23:59 UTC

[jira] [Updated] (SQOOP-3074) Fix Avro import not to fail with Javac errors in case of non UTF-8 locale

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

Attila Szabo updated SQOOP-3074:
--------------------------------
    Attachment: SQOOP-3074.patch

> 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
(v6.3.4#6332)