Skip to content

Commit

Permalink
[SPARK-26103][SQL][FOLLOW-UP] Use string-interpolation to show the co…
Browse files Browse the repository at this point in the history
…nfig key.

## What changes were proposed in this pull request?

This is a follow-up of #23169.
We should've used string-interpolation to show the config key in the warn message.

## How was this patch tested?

Existing tests.

Closes #24217 from ueshin/issues/SPARK-26103/s.

Authored-by: Takuya UESHIN <ueshin@databricks.com>
Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
  • Loading branch information
ueshin authored and HyukjinKwon committed Mar 26, 2019
1 parent 90b7251 commit 529a061
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ object StringUtils extends Logging {
logWarning(
"Truncated the string representation of a plan since it was too long. The " +
s"plan had length ${length} and the maximum is ${maxLength}. This behavior " +
"can be adjusted by setting '${SQLConf.MAX_PLAN_STRING_LENGTH.key}'.")
s"can be adjusted by setting '${SQLConf.MAX_PLAN_STRING_LENGTH.key}'.")
val truncateMsg = if (maxLength == 0) {
s"Truncated plan of $length characters"
} else {
Expand Down

0 comments on commit 529a061

Please sign in to comment.