hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-15910) Improvements in Hive Unit Test by using In-memory Derby DB
Date Wed, 15 Feb 2017 20:59:41 GMT

    [ https://issues.apache.org/jira/browse/HIVE-15910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868548#comment-15868548
] 

Hive QA commented on HIVE-15910:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12852873/HIVE-15910.3.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 15 failed/errored test(s), 10238 tests executed
*Failed tests:*
{noformat}
TestDerbyConnector - did not produce a TEST-*.xml file (likely timed out) (batchId=235)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[cbo_rp_auto_join1] (batchId=3)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[join31] (batchId=81)
org.apache.hadoop.hive.cli.TestEncryptedHDFSCliDriver.testCliDriver[encryption_join_with_different_encryption_keys]
(batchId=159)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[multiMapJoin2] (batchId=152)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14] (batchId=223)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query23] (batchId=223)
org.apache.hadoop.hive.cli.TestSparkCliDriver.testCliDriver[join31] (batchId=133)
org.apache.hadoop.hive.ql.txn.compactor.TestWorker.majorPartitionWithBase (batchId=246)
org.apache.hadoop.hive.ql.txn.compactor.TestWorker.majorPartitionWithBaseMissingBuckets (batchId=246)
org.apache.hadoop.hive.ql.txn.compactor.TestWorker.majorTableNoBase (batchId=246)
org.apache.hadoop.hive.ql.txn.compactor.TestWorker.majorTableWithBase (batchId=246)
org.apache.hadoop.hive.ql.txn.compactor.TestWorker.minorPartitionWithBase (batchId=246)
org.apache.hadoop.hive.ql.txn.compactor.TestWorker.minorTableLegacy (batchId=246)
org.apache.hadoop.hive.ql.txn.compactor.TestWorker.minorTableNoBase (batchId=246)
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/3573/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/3573/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-3573/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 15 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12852873 - PreCommit-HIVE-Build

> Improvements in Hive Unit Test by using In-memory Derby DB
> ----------------------------------------------------------
>
>                 Key: HIVE-15910
>                 URL: https://issues.apache.org/jira/browse/HIVE-15910
>             Project: Hive
>          Issue Type: Test
>          Components: Tests
>            Reporter: Sankar Hariappan
>            Assignee: Wei Zheng
>         Attachments: HIVE-15910.01.patch, HIVE-15910.2.patch, HIVE-15910.3.patch
>
>
> Hive UT currently uses Derby DB with storage on disk which have some practical problems.
> 1. The run-time of Hive unit tests are high as need to operate on the disk quite often.
> 2. It can cause conflict if multiple test cases operates on the same table name (such
as table being created already exist).
> To solve these problems, we shall use an in-memory storage option of Derby DB which can
be even persisted if the test case demands that.
> https://db.apache.org/derby/docs/10.8/devguide/cdevdvlpinmemdb.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message