[
https://issues.apache.org/jira/browse/HIVE-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Vary updated HIVE-23103:
------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to master.
Thanks for the review [~Marton Bod] and [~dkuzmenko]!
> Oracle statement batching
> -------------------------
>
> Key: HIVE-23103
> URL: https://issues.apache.org/jira/browse/HIVE-23103
> Project: Hive
> Issue Type: Improvement
> Components: Transactions
> Reporter: Peter Vary
> Assignee: Peter Vary
> Priority: Major
> Fix For: 4.0.0
>
> 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.12.patch,
> HIVE-23103.12.patch, HIVE-23103.12.patch, HIVE-23103.patch
>
>
> Examine how to really get better performance for oracle statement batches.
> [Oracle JDBC
> doc|https://docs.oracle.com/cd/E11882_01/java.112/e16548/oraperf.htm#JJDBC28752]
> describes:
> {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 use:
> {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
(v8.3.4#803005)
