hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8050) Separate the client conf key from DFSConfigKeys
Date Mon, 06 Apr 2015 19:26:12 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481674#comment-14481674

Steve Loughran commented on HDFS-8050:

Given past experience, moving stuff out of {{DFSConfigKeys}} breaks code downstream.

If the client/impl stuff is split into separate interfaces, then {{DFSConfigKeys}} must declare
itself as implementing/extending all of them, to pull them back into place

> Separate the client conf key from DFSConfigKeys
> -----------------------------------------------
>                 Key: HDFS-8050
>                 URL: https://issues.apache.org/jira/browse/HDFS-8050
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
> Currently, all the conf keys are in DFSConfigKeys.  We should separate the public client
DFSConfigKeys to a new class in org.apache.hadoop.hdfs.client as described by [~wheat9] in
> For the private conf keys, they may be moved to a new class in org.apache.hadoop.hdfs.client.impl.

This message was sent by Atlassian JIRA

View raw message