[
https://issues.apache.org/jira/browse/SPARK-48388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-48388.
---------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 47272
[https://github.com/apache/spark/pull/47272]
> [M0] Fix SET behavior for scripts
> ---------------------------------
>
> Key: SPARK-48388
> URL: https://issues.apache.org/jira/browse/SPARK-48388
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 4.0.0
> Reporter: David Milicevic
> Assignee: David Milicevic
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> By standard, SET is used to set variable value in SQL scripts.
> On our end, SET is configured to work with some Hive configs, so the grammar
> is a bit messed up and for that reason it was decided to use SET VAR instead
> of SET to work with SQL variables.
> This is not by standard and we should figure out the way to be able to use
> SET for SQL variables and forbid setting of Hive configs from SQL scripts.
>
> For more details, design doc can be found in parent Jira item.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
