Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.4.0
-
Reviewed
Description
- there are some places in the code that have to check for UnsupportedCharsetException when explicitly using the charset name "UTF-8"
- using StandardCharsets.UTF_8 is more efficient because the Java libs usually have to look up the charsets when you provide it as String param instead
- also stop using Guava Charsets and use StandardCharsets
Attachments
Issue Links
- is related to
-
HADOOP-19041 further use of StandardCharsets
- Resolved
-
YARN-11647 more places to use StandardCharsets
- Resolved
- links to