[ https://issues.apache.org/jira/browse/SQOOP-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733694#comment-15733694 ]
Hudson commented on SQOOP-3074: ------------------------------- SUCCESS: Integrated in Jenkins build Sqoop-hadoop100 #1045 (See [https://builds.apache.org/job/Sqoop-hadoop100/1045/]) SQOOP-3074: Fix Avro import not to fail with Javac errors in case of non (maugli: [https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=5771a2da5fc071ca8f80f222e8468a29419e845e]) * (edit) src/java/org/apache/sqoop/orm/AvroSchemaGenerator.java * (edit) src/java/org/apache/sqoop/avro/AvroUtil.java * (edit) src/java/org/apache/sqoop/orm/ClassWriter.java > 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)