[ https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762925#comment-16762925 ]
Íñigo Goiri commented on HADOOP-16073: -------------------------------------- The main issue I see with pushing this is having hundreds of files modified across 5+ submodules. I think we need to stage this mainly because verifying nothing breaks might be tough. In terms of changes, there are: # Switching from {{Charset.forName("UTF-8")}} to {{StandardCharsets.UTF_8}} (which avoid {{UnsupportedEncodingException}}). Actually, we could even do one just to remove "UTF-8". # Getting rid of {{com.google.common.base.Charsets}}. Let's see if we can remove guava from a couple subprojects with this. What about we split this for these to changes and per modules (e.g., hadoop-common, hadoop-hdfs...)? I know that it will be a lot of management work but I think is worth being safe here. > Use JDK1.7 StandardCharsets > --------------------------- > > Key: HADOOP-16073 > URL: https://issues.apache.org/jira/browse/HADOOP-16073 > Project: Hadoop Common > Issue Type: Improvement > Affects Versions: 3.2.0 > Reporter: BELUGA BEHR > Assignee: BELUGA BEHR > Priority: Major > Attachments: HADOOP-16073.1.patch > > > Use Java 1.7 > [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html]. > Every JDK must now include support for several common charsets. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org