This is an automated email from the ASF dual-hosted git repository.

pdallig pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/zeppelin.git


The following commit(s) were added to refs/heads/master by this push:
     new 58af379  [ZEPPELIN-5224] Suppress ConfigurationException stack trace
58af379 is described below

commit 58af3791eebeecaaae7311d1a96d33be90c1dedc
Author: Philipp Dallig <[email protected]>
AuthorDate: Wed Jan 27 09:46:13 2021 +0100

    [ZEPPELIN-5224] Suppress ConfigurationException stack trace
    
    ### What is this PR for?
    This PR outputs the stack trace only in debug mode.
    
    ### What type of PR is it?
    - Improvement
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-5224
    
    ### How should this be tested?
    * CI
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No
    
    Author: Philipp Dallig <[email protected]>
    
    Closes #4034 from Reamer/configuration_logging and squashes the following 
commits:
    
    5fbed4c3c [Philipp Dallig] Output stack trace only in debug mode
---
 .../src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java  | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git 
a/zeppelin-interpreter/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java
 
b/zeppelin-interpreter/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java
index 5b272d3..471445c 100644
--- 
a/zeppelin-interpreter/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java
+++ 
b/zeppelin-interpreter/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java
@@ -82,7 +82,8 @@ public class ZeppelinConfiguration {
      try {
       loadXMLConfig(filename);
     } catch (ConfigurationException e) {
-      LOGGER.warn("Failed to load configuration, proceeding with a default", 
e);
+      LOGGER.warn("Failed to load XML configuration, proceeding with a 
default,for a stacktrace activate the debug log");
+      LOGGER.debug("Failed to load XML configuration", e);
     }
   }
 

Reply via email to