[
https://issues.apache.org/jira/browse/HADOOP-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486590
]
Owen O'Malley commented on HADOOP-1197:
---------------------------------------
> Perhaps a clarification in the javadoc would be sufficient?
In my opinion, no. Hadoop is a framework for distributed programming and the
functions as they exist right now don't work in that context.
I'd propose that Nutch have a PluginRegistry that has an
IdentityHashMap<Configuration, Map<String, Object>> or possibly a WeakHashMap.
That would allow you to look up objects based a configuration without
pretending that the Configuration was going to store the object in some
portable way.
> 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.13.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.
