GitHub user 1ambda opened a pull request:

    https://github.com/apache/zeppelin/pull/2179

    [ZEPPELIN-2211 Too many WARN logs: "Couldn't get interpreter editor setting'

    ### What is this PR for?
    
    every time we insert invalid backend magic (e.g `sparc`), 
`InterpreterSettingManager` throws WARN log. 
    
    I changed the log level to debug because
    
    - WARN level should not be used for this kind of situation. 
    - It's not useful for users. So info level is not proper as well.
    
    I attached a screenshot.
    
    ### What type of PR is it?
    [Improvement]
    
    ### Todos
    
    NONE
    
    ### What is the Jira issue?
    
    [ZEPPELIN-2211](https://issues.apache.org/jira/browse/ZEPPELIN-2211)
    
    ### How should this be tested?
    
    - Insert invalid magic in your paragraph. For example `sparc` or `marcdown`
    
    ### Screenshots (if appropriate)
    
    
![interpreter_setting_manager](https://cloud.githubusercontent.com/assets/4968473/24235266/cbecbbf4-0fdf-11e7-9fcc-f1a95a5e82ab.gif)
    
    ### Questions:
    * Does the licenses files need update? - NO
    * Is there breaking changes for older versions? - NO
    * Does this needs documentation? - NO


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/1ambda/zeppelin 
ZEPPELIN-2211/change-log-level-ISM-NPE

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2179.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2179
    
----
commit e333c1cbec55372fca6ca9013c17e1e6f1997146
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-23T06:39:39Z

    fix: Change log level to debug from warn

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to