You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2026/01/30 17:56:00 UTC
[jira] [Resolved] (HIVE-29408) Use in-memory database in tests using qt:database:derby option
[ https://issues.apache.org/jira/browse/HIVE-29408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stamatis Zampetakis resolved HIVE-29408.
----------------------------------------
Fix Version/s: Not Applicable
Resolution: Won't Fix
> Use in-memory database in tests using qt:database:derby option
> --------------------------------------------------------------
>
> Key: HIVE-29408
> URL: https://issues.apache.org/jira/browse/HIVE-29408
> Project: Hive
> Issue Type: Task
> Components: Test
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Labels: pull-request-available
> Fix For: Not Applicable
>
>
> There are many JDBC storage handler tests that create and use Derby databases by using the qt:database:derby option. The databases are currently persisted in the file-system but this can significantly slow-down the tests especially in environments (CI) where I/O operations are slow.
> Derby supports creating fully in-memory databases that are not bound to the I/O performance of the underlying filesystem. The goal of this ticket is to use in-memory Derby databases whenever the qt:database:derby option is used in tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)