hadoop-common-dev mailing list archives

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

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

Hadoop QA commented on HADOOP-1197:
-----------------------------------

+1

http://issues.apache.org/jira/secure/attachment/12356896/no-object-get.patch applied and successfully
tested against trunk revision r536000.

Test results:   http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/122/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/122/console

> 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
>
>         Attachments: no-object-get.patch
>
>
> 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.


Mime
View raw message