tajo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jihoon Son (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TAJO-1803) Use in-memory derby as the default catalog for unit tests
Date Tue, 01 Sep 2015 13:03:45 GMT

     [ https://issues.apache.org/jira/browse/TAJO-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jihoon Son resolved TAJO-1803.
------------------------------
    Resolution: Fixed

Committed to master and branch-0.11.0.

> Use in-memory derby as the default catalog for unit tests
> ---------------------------------------------------------
>
>                 Key: TAJO-1803
>                 URL: https://issues.apache.org/jira/browse/TAJO-1803
>             Project: Tajo
>          Issue Type: Task
>          Components: Unit Test
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>             Fix For: 0.11.0
>
>
> We are currently using MemStore which is designed to provide the same interface with
AbstractDBStore. This incurs two problems.
> * The major problem is that AbstractDBStore is not tested properly by unit testing. The
logic to access catalog is separated into MemStore and AbstractDBStore, and only MemStore
is tested.
> * We have to implement both AbstractDBStore and MemStore whenever we modify the catalog
interface even though MemStore is used only in unit testing. This is an unnecessary burden
to developers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message