[
https://issues.apache.org/jira/browse/HIVE-15414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vihang Karajgaonkar updated HIVE-15414:
---------------------------------------
Description:
While analyzing the console output of pre-commit console logs, I noticed that
TestNegativeCliDriver batchSize ~770 qfiles which doesn't look right.
2016-12-09 22:23:58,945 DEBUG [TestExecutor] ExecutionPhase.execute:96 PBatch:
QFileTestBatch [batchId=84, size=774, driver=TestNegativeCliDriver,
queryFilesProperty=qfile,
name=84-TestNegativeCliDriver-nopart_insert.q-input41.q-having1.q-and-771-more..
I think {{qFileTest.clientNegative.batchSize = 1000}} in
{{test-configuration2.properties}} is probably the reason.
was:
While analyzing the console output of pre-commit console logs, I noticed that
TestNegativeCliDriver batchSize ~770 qfiles which doesn't look right.
2016-12-09 22:23:58,945 DEBUG [TestExecutor] ExecutionPhase.execute:96 PBatch:
QFileTestBatch [batchId=84, size=774, driver=TestNegativeCliDriver,
queryFilesProperty=qfile,
name=84-TestNegativeCliDriver-nopart_insert.q-input41.q-having1.q-and-771-more..
I think {{qFileTest.clientNegative.batchSize = 1000}} in
{{test-configuration2.properties}} is probably the batchSize is the reason.
> Fix batchSize for TestNegativeCliDriver
> ---------------------------------------
>
> Key: HIVE-15414
> URL: https://issues.apache.org/jira/browse/HIVE-15414
> Project: Hive
> Issue Type: Sub-task
> Reporter: Vihang Karajgaonkar
> Assignee: Vihang Karajgaonkar
> Priority: Minor
>
> While analyzing the console output of pre-commit console logs, I noticed that
> TestNegativeCliDriver batchSize ~770 qfiles which doesn't look right.
> 2016-12-09 22:23:58,945 DEBUG [TestExecutor] ExecutionPhase.execute:96
> PBatch: QFileTestBatch [batchId=84, size=774, driver=TestNegativeCliDriver,
> queryFilesProperty=qfile,
> name=84-TestNegativeCliDriver-nopart_insert.q-input41.q-having1.q-and-771-more..
>
> I think {{qFileTest.clientNegative.batchSize = 1000}} in
> {{test-configuration2.properties}} is probably the reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
