-
Notifications
You must be signed in to change notification settings - Fork 2.9k
dataflow: avoid importing log4j at all #6599
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
dataflow: avoid importing log4j at all #6599
Conversation
be6fb08
to
92eceb2
Compare
Hopefully fixes #5875 |
You may need to drop the beam version for some of these samples for tests to pass. But raise the version to ≥ 2.32.0. See #5875 (comment) Reorder imports too. |
Fixed lint issues. For the spanner sample, I'm trying Beam 2.32, if that passes I'll try 2.33 since we know something's broken with 2.34. |
I noticed that the Spanner sample was using Java 8, which ends its support in 3 months. Updating to Java 11, maybe that'll fix the failing tests as well. |
Java 11 didn't fix the tests, but downgrading to Beam 2.33 works for now. We still need to investigate why Beam 2.34 breaks SpannerIO. cc: @jsimonweb @skuruppu @ansh0l -- tests for the SpannerIO sample with Beam 2.34 are still a blocker to upgrade versions (#5875) |
@davidcavazos I will investigate separately on beam 2.34 issue. I'm assuming that for now, things are working with beam 2.33 in place. |
Remove any direct dependencies of log4j and use slf4j instead, as recommended by the documentation, and update to Beam 2.34 which doesn't depend on log4j.
Confirmed with
mvn dependency:tree | grep log4j-api
that there are no direct or indirect dependency instances of log4j on any sample by doing this.pom.xml
parent set to latestshared-configuration
mvn clean verify
requiredmvn -P lint checkstyle:check
requiredmvn -P lint clean compile pmd:cpd-check spotbugs:check
advisory only