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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.7
• Assignee: Attila Szabo
• Reporter: Attila Szabo
• Created: 08/Dec/16 18:22
• Updated: 16/Jun/17 04:28
• Resolved: 08/Dec/16 22:08

Description

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.

Issue Links

• links to: Review board