[
https://issues.apache.org/jira/browse/ASTERIXDB-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343647#comment-16343647
]
ASF subversion and git services commented on ASTERIXDB-1554:
------------------------------------------------------------
Commit 06f16cabaa4b6266b844362e1718ba5721d8c2d7 in asterixdb's branch
refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=06f16ca ]
[ASTERIXDB-1554][CONF] Do Not Override Logger Config
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Do not override logger config for hyracks/asterix
roots if they are already configured.
Change-Id: Iff7ed7c094d9044f5959f9e24713302af9774786
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2335
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Michael Blow <[email protected]>
> Global reset of org.apache.* loggers occurs after logging
> ---------------------------------------------------------
>
> Key: ASTERIXDB-1554
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1554
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: *DB - AsterixDB
> Reporter: Michael Blow
> Assignee: Murtadha Hubail
> Priority: Major
>
> NC and CC service startup resets logging level as configured, with a default
> of WARNING. As this reset takes place after some startup code has run, it
> can be confusing to tell what will be logged.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
