You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2021/02/08 13:52:00 UTC

[jira] [Resolved] (SPARK-33438) set -v couldn't dump all the conf entries

     [ https://issues.apache.org/jira/browse/SPARK-33438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon resolved SPARK-33438.
----------------------------------
    Fix Version/s: 3.1.2
                   3.0.2
       Resolution: Fixed

Issue resolved by pull request 30363
[https://github.com/apache/spark/pull/30363]

> set -v couldn't dump all the conf entries
> -----------------------------------------
>
>                 Key: SPARK-33438
>                 URL: https://issues.apache.org/jira/browse/SPARK-33438
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.0.1
>            Reporter: Linhong Liu
>            Assignee: Linhong Liu
>            Priority: Major
>             Fix For: 3.0.2, 3.1.2
>
>
> since scala object is lazy init, it won't be load until some code touched it. For SQL conf entries, it won't be registered if the conf object is never touched. So "set -v" couldn't dump all the defined configs (even if it says so)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org