hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-5265) Direct SQL fallback broken on Postgres
Date Thu, 12 Sep 2013 10:59:51 GMT


Hive QA commented on HIVE-5265:

{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 3091 tests passed

Test results:
Console output:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.
> Direct SQL fallback broken on Postgres
> --------------------------------------
>                 Key: HIVE-5265
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>            Priority: Critical
>         Attachments: HIVE-5265.D12861.1.patch
> See HIVE-5264. Postgres aborts transaction on any failed query, so the fallback doesn't
> Original code used to do rollback/restart tx on SQL failure, but then it was removed
to allow usage in cases like dropTable/etc., where there's external tx present and we cannot
partially rollback.
> Looks like the solution for now is to reinstate the rollback/reopen, and prohibit the
usage inside external transactions.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message