Using tailored log4j2 file for application

This removes the thread name, which is typically an implementation detail that most users will not need to see.

Author: rjrudin

flux-cli/build.gradle

@@ -88,14 +88,6 @@ application {
   applicationDefaultJvmArgs = ['--add-opens', 'java.base/java.nio=ALL-UNNAMED', '--add-opens', 'java.base/java.net=ALL-UNNAMED',
                                '--add-opens', 'java.base/java.lang=ALL-UNNAMED', '--add-opens', 'java.base/java.util=ALL-UNNAMED',
                                '--add-opens', 'java.base/java.util.concurrent=ALL-UNNAMED']
-
-  // For now, the log4j2 config we use for tests is suitable for production usage as well. So the log4j2 file is
-  // included in the "conf" directory, which is included on the Flux classpath via the start-script.txt file.
-  // Reference for this - https://docs.gradle.org/current/dsl/org.gradle.api.plugins.JavaApplication.html .
-  applicationDistribution.from("src/test/resources") {
-    include "log4j2.properties"
-    into "conf"
-  }
 }
 
 // Modifies the application's start script to use our modified one that adds jars in the "./ext" folder to the classpath.

flux-cli/src/dist/conf/log4j2.properties

@@ -0,0 +1,50 @@
+# The root logger with appender name
+rootLogger = INFO, STDOUT
+
+# Assign STDOUT a valid appender & define its layout
+appender.console.name = STDOUT
+appender.console.type = Console
+appender.console.layout.type = PatternLayout
+#appender.console.layout.pattern = %d{yy/MM/dd HH:mm:ss} [%tn] %p %c: %m%n
+appender.console.layout.pattern = %d{yy/MM/dd HH:mm:ss} %c: %m%n
+
+logger.marklogicclient.name=com.marklogic.client
+logger.marklogicclient.level=WARN
+logger.marklogicspark.name=com.marklogic.spark
+logger.marklogicspark.level=INFO
+
+logger.flux.name=com.marklogic.flux
+logger.flux.level=INFO
+
+# This logs write failures at the "warn" level in a verbose way.
+logger.writeBatcherImpl.name=com.marklogic.client.datamovement.impl.WriteBatcherImpl
+logger.writeBatcherImpl.level=ERROR
+
+# The following both log errors at the ERROR level, but that is usually too verbose. The user can instead include
+# "--stacktrace" to see a single stacktrace when the tool catches an Exception.
+logger.sparkutils.name=org.apache.spark.util.Utils
+logger.sparkutils.level=FATAL
+logger.sparkexecutor.name=org.apache.spark.executor.Executor
+logger.sparkexecutor.level=FATAL
+logger.sparktasksetmanager.name=org.apache.spark.scheduler.TaskSetManager
+logger.sparktasksetmanager.level=FATAL
+
+logger.sparksql.name=org.apache.spark.sql
+logger.sparksql.level=FATAL
+
+logger.spark.name=org.apache.spark
+logger.spark.level=ERROR
+logger.sparkproject.name=org.sparkproject
+logger.sparkproject.level=WARN
+logger.hadoop.name=org.apache.hadoop
+logger.hadoop.level=ERROR
+logger.parquet.name=org.apache.parquet
+logger.parquet.level=WARN
+logger.orc.name=org.apache.orc
+logger.orc.level=WARN
+
+# Jena has a fix to ignore "Unrecognized property - 'http://javax.xml.XMLConstants/property/accessExternalDTD'" errors
+# from Woodstox, but Hadoop has its own version of Woodstox that Jena isn't aware of. The error is not relevant for
+# a user, so it's suppressed here.
+logger.jenaxmlinput.name=org.apache.jena.util.JenaXMLInput
+logger.jenaxmlinput.level=FATAL

flux-cli/src/test/resources/log4j2.properties

@@ -12,7 +12,6 @@ logger.marklogicclient.level=WARN
 logger.marklogicspark.name=com.marklogic.spark
 logger.marklogicspark.level=INFO
 
-# Temporary name until we decide on a real name.
 logger.flux.name=com.marklogic.flux
 logger.flux.level=INFO