[
https://issues.apache.org/jira/browse/HIVE-23093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085869#comment-17085869
]
Hive QA commented on HIVE-23093:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/13000204/HIVE-23093.4.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 17130 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/21722/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/21722/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-21722/
Messages:
{noformat}
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 13000204 - PreCommit-HIVE-Build
> Create new metastore config value for jdbc max batch size
> ---------------------------------------------------------
>
> Key: HIVE-23093
> URL: https://issues.apache.org/jira/browse/HIVE-23093
> Project: Hive
> Issue Type: Improvement
> Reporter: Marton Bod
> Assignee: Marton Bod
> Priority: Major
> Attachments: HIVE-23093.1.patch, HIVE-23093.2.patch,
> HIVE-23093.2.patch, HIVE-23093.3.patch, HIVE-23093.4.patch
>
>
> In order to reduce the number of network calls to the metastore DB, there is
> an effort to batch acid/locking DB calls where it makes sense. Existing
> metastore config params do not provide a suitable, generic option to control
> the jdbc statement max batch size. Solution is to create a new config param,
> and use that in the appropriate batching calls in TxnHandler.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
