[
https://issues.apache.org/jira/browse/HADOOP-18931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854945#comment-17854945
]
ASF GitHub Bot commented on HADOOP-18931:
-----------------------------------------
virajjasani commented on PR #6197:
URL: https://github.com/apache/hadoop/pull/6197#issuecomment-2167335766
My bad, i misunderstood this earlier. The recommendation was to use
`assertj-core` jar location to test test ClassUtil functions (rather than using
log4j jar location), i was under the impression that the recommendation was to
use assertj for all assertions in the test class.
Latest revision: using assertj-core jar location to test ClassUtil
functions, so that even if log4j implementation changes, the tests should not
be impacted.
> FileSystem.getFileSystemClass() to log at debug the jar the .class came from
> ----------------------------------------------------------------------------
>
> Key: HADOOP-18931
> URL: https://issues.apache.org/jira/browse/HADOOP-18931
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 3.3.6
> Reporter: Steve Loughran
> Priority: Minor
> Labels: pull-request-available
>
> we want to be able to log the jar the filesystem implementation class, so
> that we can identify which version of a module the class came from.
> this is to help track down problems where different machines in the cluster
> or the .tar.gz bundle is out of date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
