[
https://issues.apache.org/jira/browse/HIVE-15910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865657#comment-15865657
]
ASF GitHub Bot commented on HIVE-15910:
---------------------------------------
GitHub user sankarh opened a pull request:
https://github.com/apache/hive/pull/147
HIVE-15910: Improvements in Hive Unit Test by using In-memory Derby DB
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sankarh/hive HIVE-15910
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/147.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #147
----
commit 4c6596e94524eb8ac0066e1371ed6ceb2c650036
Author: Sankar Hariappan <mailtosank...@gmail.com>
Date: 2017-02-14T11:39:02Z
HIVE-15910: Improvements in Hive Unit Test by using In-memory Derby DB
----
> 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 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)
