[GitHub] [nifi] bbende commented on issue #3427: NIFI-6201 Suppressed stacktraces for expected error conditions (conne…

[GitBox <gi...@apache.org>]

bbende commented on issue #3427: NIFI-6201 Suppressed stacktraces for expected error conditions (conne…
URL: https://github.com/apache/nifi/pull/3427#issuecomment-481782496
 
 
   I don't have too strong of a preference, but for the bundle case could we just append the message of the exception to the errorMessage string, and then have a debug option to log the whole stracktrace? This would be kind of similar to how our exception mappers work for the REST API.
   
   Something like:
   ```
   logger.error("Could not create Processor of type " + type + " for ID " + identifier + " due to: " + pie.getMessage() + "; creating \"Ghost\" implementation");
   if (logger.isDebugEnabled()) {
     logger.debug(e.getMessage(), e);
   }
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services