-
Notifications
You must be signed in to change notification settings - Fork 203
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Switch JDBC driver to log4j 2.17.1 from log4j 1.x
- removed hard-coded compile time dependency on log4j 1.x from entire SnappyData code-base (the underlying Spark still depends on log4j 1.x) - removed code dependencies on log4j and instead use slf4j - update store link that removes log4j 1.x dependency rather supports both 2.x and 1.x - JDBC driver packaging now includes log4j 2.x using a special "shadowInclude" configuration that includes the dependencies only in the shadow jar - also explicitly exlude log4j 1.x resources and Log4j1Configurator implementation from the JDBC driver's shadow jar to completely eliminate all traces for log4j 1.x - code that required explicit log4j references (e.g. to change log-level temporarily) now uses the methods from ClientSharedUtils that has adapters for both log4j 2.x and 1.x - ensure log4j init from store layer rather than default spark route - updated version to 1.3.0.1 from 1.3.0 - core/cluster and other components still continue to use log4j 1.x due to underlying Spark - increased gradle max-memory to 3G from 2G - updated license header templates to year 2022 from 2021 Fixes for some test failures - allow JAVA_HOME to be inherited across VMs including the independent Spark/SnappyData clusters launched by the tests by writing it to spark-env.sh; this allows one to run the SnappyData test suites by setting JAVA_HOME to Java8 while the system JDK can be different - added explicit "bind-address=localhost" in many tests that were failing due to automatically determined bind address being unusable (e.g. the one used by docker/VM/VPN) - fixed URL for cassandra download in CassandraSnappyDUnitTest
- Loading branch information
Showing
41 changed files
with
204 additions
and
192 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.