[
https://issues.apache.org/jira/browse/HDFS-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487632#comment-14487632
]
Aaron T. Myers commented on HDFS-8101:
--------------------------------------
+1, the patch looks good to me. Good sleuthing, Sean.
I'm going to commit this momentarily.
> 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
> 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)
