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

vanzin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new 93c6d2a  [SPARK-27215][CORE] Correct the kryo configurations
93c6d2a is described below

commit 93c6d2a198d1b3070eea32210042873c68d0d5f7
Author: Lantao Jin <[email protected]>
AuthorDate: Wed Mar 20 14:27:05 2019 -0700

    [SPARK-27215][CORE] Correct the kryo configurations
    
    ## What changes were proposed in this pull request?
    
    ```scala
    val KRYO_USE_UNSAFE = ConfigBuilder("spark.kyro.unsafe")
        .booleanConf
        .createWithDefault(false)
    
      val KRYO_USE_POOL = ConfigBuilder("spark.kyro.pool")
        .booleanConf
        .createWithDefault(true)
    ```
    **kyro should be kryo**
    
    ## How was this patch tested?
    
    no need
    
    Closes #24156 from LantaoJin/SPARK-27215.
    
    Authored-by: Lantao Jin <[email protected]>
    Signed-off-by: Marcelo Vanzin <[email protected]>
---
 core/src/main/scala/org/apache/spark/internal/config/Kryo.scala | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core/src/main/scala/org/apache/spark/internal/config/Kryo.scala 
b/core/src/main/scala/org/apache/spark/internal/config/Kryo.scala
index 7873141..717a099 100644
--- a/core/src/main/scala/org/apache/spark/internal/config/Kryo.scala
+++ b/core/src/main/scala/org/apache/spark/internal/config/Kryo.scala
@@ -34,11 +34,11 @@ private[spark] object Kryo {
     .toSequence
     .createWithDefault(Nil)
 
-  val KRYO_USE_UNSAFE = ConfigBuilder("spark.kyro.unsafe")
+  val KRYO_USE_UNSAFE = ConfigBuilder("spark.kryo.unsafe")
     .booleanConf
     .createWithDefault(false)
 
-  val KRYO_USE_POOL = ConfigBuilder("spark.kyro.pool")
+  val KRYO_USE_POOL = ConfigBuilder("spark.kryo.pool")
     .booleanConf
     .createWithDefault(true)
 


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

Reply via email to