This is an automated email from the ASF dual-hosted git repository.

gurwls223 pushed a commit to branch branch-3.2
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/branch-3.2 by this push:
     new 101f720  [SPARK-32920][CORE][FOLLOW-UP] Fix string interpolator in the 
log
101f720 is described below

commit 101f720cc95e86e8e8b5a1d01aeb8718bfba277d
Author: yi.wu <[email protected]>
AuthorDate: Fri Aug 13 21:44:22 2021 +0900

    [SPARK-32920][CORE][FOLLOW-UP] Fix string interpolator in the log
    
    ### What changes were proposed in this pull request?
    
    fix string interpolator
    
    ### Why are the changes needed?
    
    To log the correct stage info.
    
    ### Does this PR introduce _any_ user-facing change?
    
    No.
    
    ### How was this patch tested?
    
    Pass existed tests.
    
    Closes #33738 from Ngone51/fix.
    
    Authored-by: yi.wu <[email protected]>
    Signed-off-by: Hyukjin Kwon <[email protected]>
    (cherry picked from commit a47ceaf5492040063e31e17570678dc06846c36c)
    Signed-off-by: Hyukjin Kwon <[email protected]>
---
 core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala 
b/core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
index b276de1..c45e7f8 100644
--- a/core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
+++ b/core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
@@ -1309,7 +1309,7 @@ private[spark] class DAGScheduler(
           s"${stage.shuffleDep.getMergerLocs.map(_.host).mkString(", ")}")
       } else {
         stage.shuffleDep.setShuffleMergeEnabled(false)
-        logInfo("Push-based shuffle disabled for $stage (${stage.name})")
+        logInfo(s"Push-based shuffle disabled for $stage (${stage.name})")
       }
     }
   }

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to