hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1197) The misleading Configuration.set(String, Object) should be removed
Date Tue, 08 May 2007 05:00:15 GMT

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

Owen O'Malley updated HADOOP-1197:

    Status: Patch Available  (was: Open)

This patch deprecates the offending methods. It also adds a method "getRaw" that returns the
value from the config without variable replacements being done. (Some of the code was using
the fact that get(String, Object) wasn't do replacement.) It also replaces a couple spots
where dfs was putting an enumeration in to the config using these methods.

> The misleading Configuration.set(String, Object) should be removed
> ------------------------------------------------------------------
>                 Key: HADOOP-1197
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1197
>             Project: Hadoop
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.12.2
>            Reporter: Owen O'Malley
>         Assigned To: Owen O'Malley
>            Priority: Minor
>             Fix For: 0.14.0
> I think that the confusing methods in Configuration:
>   set(String, Object)
>   getObject(String)
>   get(String, Object)
> should be deprecated. Users expect them to work and in a distributed environment, there
is almost no way to make them work correctly. If some user really needs the functionality,
we should implement it right and require that the objects be Writable and serialize them into
the Configuration.
> Thoughts?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message