[
https://issues.apache.org/jira/browse/HIVE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810849#comment-13810849
]
Hive QA commented on HIVE-5626:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12611238/HIVE-5626.02.patch
{color:green}SUCCESS:{color} +1 4547 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/88/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/88/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
> 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.02.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)
