hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8101) DFSClient use of non-constant DFSConfigKeys pulls in WebHDFS classes at runtime
Date Sun, 27 Mar 2016 00:55:25 GMT

     [ https://issues.apache.org/jira/browse/HDFS-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Haohui Mai updated HDFS-8101:
-----------------------------
    Fix Version/s:     (was: 2.8.0)
                   2.7.3

> DFSClient use of non-constant DFSConfigKeys pulls in WebHDFS classes at runtime
> -------------------------------------------------------------------------------
>
>                 Key: HDFS-8101
>                 URL: https://issues.apache.org/jira/browse/HDFS-8101
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs-client
>    Affects Versions: 2.7.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Minor
>             Fix For: 2.7.3
>
>         Attachments: HDFS-8101.1.patch.txt
>
>
> Previously, all references to DFSConfigKeys in DFSClient were compile time constants
which meant that normal users of DFSClient wouldn't resolve DFSConfigKeys at run time. As
of HDFS-7718, DFSClient has a reference to a member of DFSConfigKeys that isn't compile time
constant (DFS_CLIENT_KEY_PROVIDER_CACHE_EXPIRY_DEFAULT).
> Since the class must be resolved now, this particular member
> {code}
> public static final String  DFS_WEBHDFS_AUTHENTICATION_FILTER_DEFAULT = AuthFilter.class.getName();
> {code}
> means that javax.servlet.Filter needs to be on the classpath.
> javax-servlet-api is one of the properly listed dependencies for HDFS, however if we
replace {{AuthFilter.class.getName()}} with the equivalent String literal then downstream
folks can avoid including it while maintaining compatibility.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message