GitHub user brianghig opened a pull request:

    https://github.com/apache/incubator-nifi/pull/59

    Processor Logger using same level as message for Throwables

    Processor Loggers will now use the same Logger level for Throwables as is 
used for messages. Previously, enabling DEBUG was the only way to see 
stacktraces from logged throwables when running in INFO, WARN, or ERROR levels.

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

    $ git pull https://github.com/brianghig/incubator-nifi 
ProcessorLog-ExceptionsUseSameLevels

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

    https://github.com/apache/incubator-nifi/pull/59.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 #59
    
----
commit 29b4e56a61dc7125e10d7e5d70a0123485717b4d
Author: Brian Ghigiarelli <[email protected]>
Date:   2015-04-22T15:32:36Z

    Merge pull request #1 from apache/develop
    
    Merging latest NiFi to my fork

commit 421ad8fb133d3bab32bc20d98011e9dfa0caff99
Author: Brian Ghigiarelli <[email protected]>
Date:   2015-05-14T00:32:23Z

    Merge pull request #2 from apache/develop
    
    Merging latest Apache NiFi to fork

commit ce16aab6c57a5b3d771149a1720471b980cf5a1c
Author: Brian Ghigiarelli <[email protected]>
Date:   2015-05-21T12:42:32Z

    Merge pull request #4 from apache/develop
    
    Merging latest Apache NiFi develop branch

commit 710914675f4b5cae727092c4779e82b17dd2b145
Author: Brian Ghigiarelli <[email protected]>
Date:   2015-05-26T15:03:40Z

    Processor Loggers will now use the same Logger Level for throwables as they 
do for the log messages. Previously, enabling DEBUG was the only way to see 
stacktraces from throwables in INFO, WARN, or ERROR levels

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to