[ 
https://issues.apache.org/jira/browse/NIFI-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850046#comment-17850046
 ] 

David Handermann edited comment on NIFI-13265 at 5/28/24 2:30 PM:
------------------------------------------------------------------

Thanks for highlighting those examples [~dstiegli1]. The {{due to...}} syntax 
is an artifact of legacy behavior that did not properly handle {{Throwable}} 
arguments.  When making the changes, {{due to}} should be removed completely, 
as follows based on the example you provided:
{noformat}
 getLogger().error("Routing to failure since failed to retrieve content from {} 
for {}", filenameValue, originalFlowFile, e);{noformat}


was (Author: exceptionfactory):
Thanks for highlighting those examples [~dstiegli1]. The {{due to...}} syntax 
is an artifact of legacy behavior that did not properly handle {{Throwable}} 
examples.  When making the changes, {{due to}} should be removed completely, as 
follows based on the example you provided:


{noformat}
 getLogger().error("Routing to failure since failed to retrieve content from {} 
for {}", filenameValue, originalFlowFile, e);{noformat}

> Remove the instantiation of Object arrays for arguments in ComponentLog log 
> and org.slf4j.Logger statements
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-13265
>                 URL: https://issues.apache.org/jira/browse/NIFI-13265
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Daniel Stieglitz
>            Assignee: Daniel Stieglitz
>            Priority: Minor
>
> There are still classes after the changes in NIFI-12075 and NIFI-12076 which 
> instantiate an Object array for ComponentLog log statements. This ticket aims 
> to remove those instantiations. In addition similar changes should be made to 
> org.slf4j.Logger statements.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to