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

Maxim Gekk updated SPARK-30892:
-------------------------------
    Description: The spark.sql.variable.substitute.depth SQL config is not used 
since Spark 2.4 inclusively. By the 
[https://github.com/apache/spark/pull/27169], the config was placed to 
SQLConf.removedSQLConfigs. And as a consequence of that when an user set it 
non-default value (1 for example),  he/she will get an exception. It is 
acceptable for configs that could impact on the behavior but not for this 
particular config. Raising of such exception will just make migration to Spark 
3.0 more difficult.  (was: The spark.sql.variable.substitute.depth SQL config 
is not used since Spark 2.4 inclusively. By the 
[https://github.com/apache/spark/pull/27169], the config was placed to 
SQLConf.removedSQLConfigs. And as a consequence of that when an user set it 
non-default value (1 for example),  he/she will get an exception. It is 
acceptable for configs that could impact on the behavior but not for this 
particular config. Raising of such exception will just make migration to Spark 
more difficult.)

> Exclude spark.sql.variable.substitute.depth from removedSQLConfigs
> ------------------------------------------------------------------
>
>                 Key: SPARK-30892
>                 URL: https://issues.apache.org/jira/browse/SPARK-30892
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Maxim Gekk
>            Priority: Major
>
> The spark.sql.variable.substitute.depth SQL config is not used since Spark 
> 2.4 inclusively. By the [https://github.com/apache/spark/pull/27169], the 
> config was placed to SQLConf.removedSQLConfigs. And as a consequence of that 
> when an user set it non-default value (1 for example),  he/she will get an 
> exception. It is acceptable for configs that could impact on the behavior but 
> not for this particular config. Raising of such exception will just make 
> migration to Spark 3.0 more difficult.



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

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

Reply via email to