[ https://issues.apache.org/jira/browse/SQOOP-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754095#comment-15754095 ]
ASF subversion and git services commented on SQOOP-3075: -------------------------------------------------------- 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 EscapeUtils (Attila Szabo) > Simplify Unicode character support in source files (introduced by SQOOP-3074) > by defining explicit locales instead of using EscapeUtils > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: SQOOP-3075 > URL: https://issues.apache.org/jira/browse/SQOOP-3075 > Project: Sqoop > Issue Type: Improvement > Reporter: Attila Szabo > Assignee: Attila Szabo > Attachments: SQOOP-3075.patch > > > Although [SQOOP-3074] achieved that Sqoop won't fail anymore with special > characters even if the locale on the caller system is not UTF-8, there's a > simpler solution to do the same thing, by tuning the compiler + classwriter > itself (by adding explicit encodings) instead of using the > StringEscapeUtils#escapeJava mechanism. > This solution seems simpler, and won't introduce any confusion around > generation of Java identifiers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)