[
https://issues.apache.org/jira/browse/HIVE-15910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873736#comment-15873736
]
Sankar Hariappan commented on HIVE-15910:
-----------------------------------------
[~wzheng]
Currently, I didn't check the performance impacts due to creation and deletion
of temp dir for each test case.
However, this can be tracked using another JIRA ticket to make the temp dir
creation only once for whole of TestWorker.
> 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: 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.
> https://db.apache.org/derby/docs/10.8/devguide/cdevdvlpinmemdb.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
