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 "Kai Zheng (JIRA)" <ji...@apache.org> on 2014/06/26 12:01:32 UTC

[jira] [Updated] (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:all-tabpanel ]

Kai Zheng updated HADOOP-10753:
-------------------------------

    Description: 
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.

  was:
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 coupling with fs stuffs.

Could anyone post your thought about this, and if confirmed, I would provide a patch for it.


> 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)