hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sankar Hariappan (JIRA)" <>
Subject [jira] [Updated] (HIVE-15910) Improvements in Hive Unit Test by using In-memory Derby DB
Date Fri, 17 Feb 2017 11:37:41 GMT


Sankar Hariappan updated HIVE-15910:
    Attachment: HIVE-15910.06.patch

[~thejas] [~wzheng]
Added Patch-06 with temp directory creation using Files.createTempDirectory method and also
added @After methods to delete the temp directory after each test case.
Please review the same.

Will add a follow-up JIRA to handle the CompactorTest constructor issue.

> Improvements in Hive Unit Test by using In-memory Derby DB
> ----------------------------------------------------------
>                 Key: HIVE-15910
>                 URL:
>             Project: Hive
>          Issue Type: Test
>          Components: Tests
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>         Attachments: HIVE-15910.01.patch, HIVE-15910.05.patch, HIVE-15910.06.patch, HIVE-15910.2.patch,
HIVE-15910.3.patch, HIVE-15910.4.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.

This message was sent by Atlassian JIRA

View raw message