[
https://issues.apache.org/jira/browse/HIVE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809526#comment-13809526
]
Ashutosh Chauhan commented on HIVE-5626:
----------------------------------------
If we have config enabled by default, then will postgres be broken or will it
choose slow datanucleus path. If postgres chooses slow DN path, will that be
for all queries or only for drop queries?
> 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
> Assignee: Sergey Shelukhin
> Priority: Minor
> Attachments: HIVE-5626.01.patch, 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)
