You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2014/06/26 17:21:25 UTC
[jira] [Commented] (HADOOP-10753) Could be better to move
CommonConfigurationKeysPublic to org.apache.hadoop.common package
[ https://issues.apache.org/jira/browse/HADOOP-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044751#comment-14044751 ]
Jason Lowe commented on HADOOP-10753:
-------------------------------------
org.apache.hadoop.conf may be a more appropriate package.
org.apache.hadoop.fs.CommonConfigurationKeysPublic is marked Public, therefore people are free to depend upon it. We can't simply move it because that break backwards compatibility. We may be able to get away with moving it then leaving a trivial derivation in org.apache.hadoop.fs via something like this:
{code}
package org.apache.hadoop.fs;
@InterfaceAudience.Public
@Deprecated
public class CommonConfigurationKeysPublic extends org.apache.hadoop.conf.CommonConfigurationKeysPublic {
}
{code}
> Could be better to move CommonConfigurationKeysPublic to org.apache.hadoop.common package
> -----------------------------------------------------------------------------------------
>
> Key: HADOOP-10753
> URL: https://issues.apache.org/jira/browse/HADOOP-10753
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Kai Zheng
> Assignee: Kai Zheng
> Priority: Minor
>
> As discussed in HADOOP-8943, it would be better to place CommonConfigurationKeysPublic into a more neutral place like org.apache.hadoop.common instead of org.apache.hadoop.fs package. This would help common facilities like security related codes avoid coupling with fs stuffs.
> Could anyone post your thought about this, and if confirmed, I would provide a patch for it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)