[
https://issues.apache.org/jira/browse/NIFI-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-13266:
------------------------------------
Description:
There are performance gains to be had when using string interpolation instead
of string concatenation hence any use of concatenation should be replaced with
parameters. See [Are concatenating strings in a Java logger is best or bad
practice?|https://www.linkedin.com/pulse/concatenating-strings-java-logger-best-bad-practice-jamsheer-t]
for more details.
The only concatenation which should be used is when a line exceeds the 200
length limit set in Checkstyle.
was:There are performance gains to be had when using string interpolation
instead of string concatenation hence any use of concatenation should be
replaced with parameters. See [Are concatenating strings in a Java logger is
best or bad
practice?|https://www.linkedin.com/pulse/concatenating-strings-java-logger-best-bad-practice-jamsheer-t]
for more details.
> Remove any use of string concatenation in logging statements
> ------------------------------------------------------------
>
> Key: NIFI-13266
> URL: https://issues.apache.org/jira/browse/NIFI-13266
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Daniel Stieglitz
> Assignee: Daniel Stieglitz
> Priority: Major
>
> There are performance gains to be had when using string interpolation instead
> of string concatenation hence any use of concatenation should be replaced
> with parameters. See [Are concatenating strings in a Java logger is best or
> bad
> practice?|https://www.linkedin.com/pulse/concatenating-strings-java-logger-best-bad-practice-jamsheer-t]
> for more details.
> The only concatenation which should be used is when a line exceeds the 200
> length limit set in Checkstyle.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)