[
https://issues.apache.org/jira/browse/HIVE-15910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870372#comment-15870372
]
Thejas M Nair commented on HIVE-15910:
--------------------------------------
Added a comment in github pull request. Its simpler to just delete the temp dir
where all tables are being created.
Also realized, that tmpdir.deleteOnExit() doesn't work unless the dir is
empty. That call would be useless.
> 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.05.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)
