[
https://issues.apache.org/jira/browse/HIVE-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183543#comment-15183543
]
Aihua Xu commented on HIVE-7532:
--------------------------------
>From my understanding on the code, the setting will be applied on one
>metastore connection. Depends on if the following query will get a new
>connection or not, such setting will not or will be applied. It's not session
>wise setting. If we want a session wise setting, we can just use property
>override for that session, right? Let me know if I misunderstand the usage.
> allow disabling direct sql per query with external metastore
> ------------------------------------------------------------
>
> Key: HIVE-7532
> URL: https://issues.apache.org/jira/browse/HIVE-7532
> Project: Hive
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
> Assignee: Navis
> Fix For: 0.14.0
>
> Attachments: HIVE-7532.1.patch.txt, HIVE-7532.2.nogen,
> HIVE-7532.2.patch.txt, HIVE-7532.3.patch.txt, HIVE-7532.4.patch.txt,
> HIVE-7532.5.patch.txt, HIVE-7532.6.patch.txt
>
>
> Currently with external metastore, direct sql can only be disabled via
> metastore config globally. Perhaps it makes sense to have the ability to
> propagate the setting per query from client to override the metastore
> setting, e.g. if one particular query causes it to fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
