You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/10/29 00:34:30 UTC
[jira] [Updated] (HIVE-5626) enable metastore direct SQL for
drop/similar queries
[ https://issues.apache.org/jira/browse/HIVE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Shelukhin updated HIVE-5626:
-----------------------------------
Attachment: HIVE-5626.patch
Simple patch adds config setting that can be disabled to disable this for DDL; by default it's enabled.
I think detecting postgres is an overkill (could be done easily though)
> enable metastore direct SQL for drop/similar queries
> ----------------------------------------------------
>
> Key: HIVE-5626
> URL: https://issues.apache.org/jira/browse/HIVE-5626
> Project: Hive
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
> Priority: Minor
> Attachments: HIVE-5626.patch
>
>
> Metastore direct SQL is currently disabled for any queries running inside external transaction (i.e. all modification queries, like dropping stuff).
> This was done to keep the strictly performance-optimization behavior when using Postgres, which unlike other RDBMS-es fails the tx on any syntax error; so, if direct SQL is broken there's no way to fall back. So, it is disabled for these cases.
> It is not as important because drop commands are rare, but we might want to address that. Either by some config setting or by making it work on non-postgres DBs.
--
This message was sent by Atlassian JIRA
(v6.1#6144)