-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-18931. FileSystem.getFileSystemClass() to log at debug the jar the .class came from #6197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
… the .class came from
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
@slfan1989 could you please review this PR? |
|
@goiri could you please review this PR? |
steveloughran
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
core looks good, just making sure that lookup code is going to work well
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/ClassUtil.java
Show resolved
Hide resolved
|
🎊 +1 overall
This message was automatically generated. |
steveloughran
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this going to be brittle across log4j? it might be better to use assertj classes
|
It is assertj: |
|
🎊 +1 overall
This message was automatically generated. |
think my concern is more when logging changes the test will break. look for a different class we know will always be found, maybe something in hadoop-auth |
|
My bad, i misunderstood this earlier. The recommendation was to use Latest revision: using assertj-core jar location to test ClassUtil functions, so that even if log4j implementation changes, the tests should not be impacted. |
|
🎊 +1 overall
This message was automatically generated. |
steveloughran
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
+1
…ss came from (#6197) Set the log level of logger org.apache.hadoop.fs.FileSystem to DEBUG to see this. Contributed by Viraj Jasani
|
merged to branch-3.4, ran new test cases. all good |
…ss came from (apache#6197) Set the log level of logger org.apache.hadoop.fs.FileSystem to DEBUG to see this. Contributed by Viraj Jasani
…ss came from (apache#6197) Set the log level of logger org.apache.hadoop.fs.FileSystem to DEBUG to see this. Contributed by Viraj Jasani
Jira: HADOOP-18931