[
https://issues.apache.org/jira/browse/SPARK-17277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjoon Hyun resolved SPARK-17277.
-----------------------------------
Resolution: Won't Fix
As mentioned in the related issue
[comment|https://github.com/apache/spark/pull/17223#issuecomment-286608743], we
will not set hive conf dynamically in order to keep session isolation.
{quote}
Since hive client is shared among all sessions, we can't set hive conf
dynamically, to keep session isolation. I think we should treat hive conf as
static sql conf, and throw exception when users try to change them.
{quote}
I'll close this issue as WON'T FIX, too.
> Set hive conf failed
> --------------------
>
> Key: SPARK-17277
> URL: https://issues.apache.org/jira/browse/SPARK-17277
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.0.0
> Reporter: Weizhong
> Priority: Minor
>
> Now we can't use "SET k=v" to set Hive conf, for example: run below SQL in
> spark-sql
> {noformat}
> set hive.exec.max.dynamic.partitions = 2000
> {noformat}
> but actually the value is 1000(default value), this is because after merge
> SPARK-15012, we don't call runSqlHive("SET k=v") when set Hive conf.
> Only those conf we will use directly on Spark is OK, like
> hive.exec.dynamic.partition.mode etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
