[
https://issues.apache.org/jira/browse/HIVE-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183184#comment-15183184
]
Aihua Xu commented on HIVE-7532:
--------------------------------
[~navis] and [~sershe] Seems I don't fully get how
meta:hive.metastore.try.direct.sql would work and wonder why it's needed. Can
you help clarify? We can provide a session level override, without affecting
the global settings, right? Are we mainly targeting this for per query level?
Can we achieving by turning on before the query and turn off after the query?
Thanks.
> 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)
