[HIVE-15910] Improvements in Hive Unit Test by using In-memory Derby DB - ASF JIRA

Log work

Agile Board

Rank to Top

Rank to Bottom

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Create sub-task

Convert to sub-task

Move

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Test
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.3.0
Component/s: Tests
Labels:
None

Description

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