[
https://issues.apache.org/jira/browse/SPARK-48388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849301#comment-17849301
]
David Milicevic commented on SPARK-48388:
-----------------------------------------
Already have ready changes. I will work on this as soon as SPARK-48342 is
completed.
> 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
> Priority: Major
>
> 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
