[query] use log4j2 #15176
Open
[query] use log4j2 #15176
+92
−338
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ehigham
changed the base branch from
ehigham/experimental-init
to
graphite-base/15176
ehigham
force-pushed
the
graphite-base/15176
branch
from
71be1cd to
e215e19
Compare
ehigham
force-pushed
the
ehigham/log4j-socker-appender
branch
from
1849ac0 to
7d9a51a
Compare
ehigham
changed the base branch from
graphite-base/15176
to
ehigham/query-cloud-credentials
This was referenced Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
Update logging infrastructure to use Log4j2 instead of Log4j1, which is deprecated. This PR:
Security Assessment
This change cannot impact the Hail Batch instance as deployed by Broad Institute in GCP