hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-23103) Oracle statement batching
Date Tue, 21 Apr 2020 04:02:00 GMT


Hive QA commented on HIVE-23103:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 17134 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[orc_llap_counters1] (batchId=57)

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed

This message is automatically generated.

ATTACHMENT ID: 13000574 - PreCommit-HIVE-Build

> Oracle statement batching
> -------------------------
>                 Key: HIVE-23103
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>            Priority: Major
>         Attachments: HIVE-23103.02.patch, HIVE-23103.03.patch, HIVE-23103.04.patch, HIVE-23103.05.patch,
HIVE-23103.06.patch, HIVE-23103.07.patch, HIVE-23103.08.patch, HIVE-23103.09.patch, HIVE-23103.10.patch,
HIVE-23103.11.patch, HIVE-23103.patch
> Examine how to really get better performance for oracle statement batches.
> [Oracle JDBC doc|]
> {quote}The Oracle implementation of standard update batching does not implement true
batching for generic statements and callable statements. Even though Oracle JDBC supports
the use of standard batching for {{Statement}} and {{CallableStatement}} objects, you
are unlikely to see performance improvement.
> {quote}
> I would look for connection properties to set, so it is handled anyway, or if not, then
> {code}
> begin
>   query1;
>   query2;
>   query3;
> end;
> {code}
> to we will have only a single roundtrip for the db.

This message was sent by Atlassian Jira

View raw message