I'm trying to pitch in a little and update components to use slf4j
parameterization, would it be helpful to remove this and simply use
the sl4j error printing facilities instead?
Thanks!
On Thu, Oct 12, 2017 at 4:20 PM, Owen O'Malley <owen.omal...@gmail.com> wrote:
> It is a very old relic from when logging the exception just gave you the
> message. It can should be replaced at some point.
>
> .. Owen
>
> On Thu, Oct 12, 2017 at 1:17 PM, dam6923 . <dam6...@gmail.com> wrote:
>>
>> Hello,
>>
>> Can someone please explain what the value of
>> org.apache.hadoop.util.StringUtils#stringifyException is? How is this
>> better than just allowing the logging framework to format the
>> exception information?
>>
>> LOG.warn("show function: {}", stringifyException(e));
>>
>> v.s.
>>
>> LOG.warn("show function: ", e);
>>
>> Thanks!
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
>> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
