HIVE-28417: Bump Log4j2 to 2.23.1 to facilitate compilation of GraalVM Native Image

[linghengqian]

What changes were proposed in this pull request?

• Bump Log4j2 to 2.23.1 to facilitate compilation of GraalVM Native Image.

Why are the changes needed?

• This PR is aimed at ensuring that HiveServer2 JDBC Driver is compatible with future versions of LOG4J as much as possible. I created a unit test at https://github.com/linghengqian/log4j2-v2231-graalvm-native-image-test to prove that the HiveServer2 JDBC Driver using apache/logging-log4j2:2.23.1 can be used under the GraalVM Native Image compiled by GraalVM CE For JDK 22.0.2.

sdk install java 8.0.422-tem
sdk install java 22.0.2-graalce
sdk use java 8.0.422-tem
sdk install maven
git clone git@github.com:linghengqian/hive.git -b log4j-bump
cd ./hive/
mvn clean install -DskipTests
mvn clean package -pl packaging -DskipTests -Pdocker
cd ../

git clone git@github.com:linghengqian/log4j2-v2231-graalvm-native-image-test.git
cd ./log4j2-v2231-graalvm-native-image-test/
sdk use java 22.0.2-graalce
./mvnw -PgenerateMetadata -DskipNativeTests -e -T1C clean test native:metadata-copy
./mvnw -PnativeTestInHive -T1C -e clean test

• See also https://github.com/apache/logging-log4j2/blob/rel/2.23.1/src/changelog/2.20.0/LOG4J2-3650_Move_tests.xml .

Moved `log4j-api` and `log4j-core` artifacts with classifier `tests` to `log4j-api-test` and `log4j-core-test` respectively. 

• See also log4j-core test-jar not published to Maven Central for 2.20.0 release logging-log4j2#1291 (comment) .

I took care of the [release notes](https://logging.apache.org/log4j/2.x/release-notes/2.20.0.html).

The difference in dependencies is caused by Maven:

for the log4j-core artifact with tests classifier Maven pulled the wrong dependencies (compile scope instead of test scope),
for the log4j-core-test artifact the real dependencies are no longer hidden: the artifact mostly contains JUnit 4 and JUnit 5 extensions, so it depends on all those libraries.

• See also Sync SLF4J 1.x and 2.x bindings logging-log4j2#1032 . The constructor of org.apache.logging.slf4j.Log4jMarker has changed.
• See also Fix handling of onMatch and onMismatch attributes in the properties configuration format logging-log4j2#2791 and When bump from 2.23.0 to 2.23.1, the status of the .properties configuration file no longer works logging-log4j2#2794 . The Log4j configuration file used by Hive contains deprecated properties .

Does this PR introduce any user-facing change?

No.

Is the change a dependency upgrade?

• Below is the output of mvn dependency:tree > ./dependency-tree.txt.

• dependency-tree.txt

How was this patch tested?

sdk install java 8.0.422-tem
sdk use java 8.0.422-tem
sdk install maven
mvn clean install -DskipTests
mvn test -Dtest=TestHplsqlLocal
mvn test -Dtest=TestHplsqlOffline

[linghengqian]

• @pgaref I don't understand why the bot didn't update the github tag after I put the PR back for review. Do you know how to make the bot update the github tag again?
• update 1st: To be honest, I can't understand the error log of https://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-5375/5/tests .

Unexpected exception java.lang.RuntimeException: Process docker failed to run in 30 seconds
 at org.apache.hadoop.hive.ql.externalDB.AbstractExternalDB.runCmd(AbstractExternalDB.java:91)
 at org.apache.hadoop.hive.ql.externalDB.AbstractExternalDB.runCmdAndPrintStreams(AbstractExternalDB.java:106)

• update 2nd: I took a moment to get to know the Jenkins UI... Looks like it should work, right?
• update 3rd: Wait Fix handling of onMatch and onMismatch attributes in the properties configuration format logging-log4j2#2791 .
• update 4th: All done.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[Aggarwal-Raghav]

@linghengqian, any reason for removing this?

[linghengqian]

• Refer to Fix handling of onMatch and onMismatch attributes in the properties configuration format logging-log4j2#2791 (comment) and https://logging.apache.org/log4j/2.x/manual/configuration.html#Properties mentioned in my PR description. According to the log4j2 committer, defining a logger no longer requires listing a loggers root node, and this loggers root node will be removed in log4j2 version 3.0.

• Or we can keep the root loggers node until log4j2 removes it in version 3.0.

Prior to version 2.6, the properties configuration requires that you list the identifiers of the appenders, filters and loggers, in a comma separated list in properties with those names. Each of those components will then be expected to be defined in sets of properties that begin with component.<.identifier>.. The identifier does not have to match the name of the component being defined but must uniquely identify all the attributes and subcomponents that are part of the component. If the list of identifiers is not present the identifier must not contain a '.'. Each individual component MUST have a "type" attribute specified that identifies the component's Plugin type.
As of version 2.6, this list of identifiers is no longer required as names are inferred upon first usage, however if you wish to use more complex identifies you must still use the list. If the list is present it will be used.

[Aggarwal-Raghav]

Had 1 question, added it as comment. Otherwise java and pom changes LGTM (+1 non-binding).