hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-8101) DFSConfigKeys pulls in WebHDFS classes at runtime
Date Wed, 08 Apr 2015 21:30:12 GMT
Sean Busbey created HDFS-8101:
---------------------------------

             Summary: 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


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