You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2017/02/14 10:28:41 UTC
[jira] [Assigned] (HIVE-15910) Improvements in Hive Unit Test by
using In-memory Derby DB
[ https://issues.apache.org/jira/browse/HIVE-15910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sankar Hariappan reassigned HIVE-15910:
---------------------------------------
> 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
>
> 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)