hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11512) Use getTrimmedStrings when reading serialization keys
Date Tue, 10 Feb 2015 07:23:35 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-11512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Harsh J updated HADOOP-11512:
       Resolution: Fixed
    Fix Version/s: 2.7.0
           Status: Resolved  (was: Patch Available)

Local mvn eclipse:eclipse passes just fine with patch. I've pushed the patch to trunk and


> Use getTrimmedStrings when reading serialization keys
> -----------------------------------------------------
>                 Key: HADOOP-11512
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11512
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 2.6.0
>            Reporter: Harsh J
>            Assignee: Ryan P
>            Priority: Minor
>             Fix For: 2.7.0
>         Attachments: HADOOP-11512.branch-2.patch, HADOOP-11512.patch, HADOOP-11512.patch,
HADOOP-11512.patch, HADOOP-11512.patch, HADOOP-11512.patch
> In the file {{hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/serializer/SerializationFactory.java}},
we grab the IO_SERIALIZATIONS_KEY config as Configuration#getStrings(…) which does not trim
the input. This could cause confusing user issues if someone manually overrides the key in
the XML files/Configuration object without using the dynamic approach.
> The call should instead use Configuration#getTrimmedStrings(…), so the whitespace is
trimmed before the class names are searched on the classpath.

This message was sent by Atlassian JIRA

View raw message