trafodion-codereview mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From selvaganesang <...@git.apache.org>
Subject [GitHub] incubator-trafodion pull request #1178: [TRAFODION-2596] Improve the log4j a...
Date Thu, 13 Jul 2017 23:02:09 GMT
GitHub user selvaganesang opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/1178

    [TRAFODION-2596] Improve the log4j and log4cxx infrastructure in Traf…

    …odion
    
    Removed setting the root logger to be the appender logger in most of
    the configuration files. This would allow T2 driver applications
    to have control over the logging in their layer to its preferred way.
    But, the logging in SQL engine layer will be controlled by the Trafodion
    engine itself.
    
    Changed the code so that the logging location and the file name is
    picked up from the config file.

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

    $ git pull https://github.com/selvaganesang/incubator-trafodion seabed_logging

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

    https://github.com/apache/incubator-trafodion/pull/1178.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 #1178
    
----
commit 4f9da0b6d4e9a56e7f7bd8692195dc809a9197af
Author: selvaganesang <selva.govindarajan@esgyn.com>
Date:   2017-07-13T22:58:13Z

    [TRAFODION-2596] Improve the log4j and log4cxx infrastructure in Trafodion
    
    Removed setting the root logger to be the appender logger in most of
    the configuration files. This would allow T2 driver applications
    to have control over the logging in their layer to its preferred way.
    But, the logging in SQL engine layer will be controlled by the Trafodion
    engine itself.
    
    Changed the code so that the logging location and the file name is
    picked up from the config file.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message