You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Jaehwa Jung (JIRA)" <ji...@apache.org> on 2015/06/17 03:57:00 UTC
[jira] [Updated] (TAJO-1648) Apply In-memory database using derby
to test cases
[ https://issues.apache.org/jira/browse/TAJO-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaehwa Jung updated TAJO-1648:
------------------------------
Description: Currently, Tajo built-in testing cluster start up MemStore. But MemStore isn't based on database. So if we write complex query for some catalog method, MemStore would be difficult to adapt the query. So, we need to consider apply DerbyStore instead of MemStore for the testing cluster. I think it would be more useful compare than file based database using derby. (was: Currently, Tajo built-in testing cluster start up MemStore. But MemStore isn't based on database. So if we write complex query for some catalog method, MemStore would be difficult to adapt the query. So, we need to consider apply DerbyStore instead of MemStore for the testing cluster. For the reference, currently DerbyStore provides in-memory database on Derby 10.x version. I think it would be more useful compare than file based database using derby.)
> Apply In-memory database using derby to test cases
> --------------------------------------------------
>
> Key: TAJO-1648
> URL: https://issues.apache.org/jira/browse/TAJO-1648
> Project: Tajo
> Issue Type: Improvement
> Components: catalog
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Fix For: 0.11.0, 0.10.2
>
>
> Currently, Tajo built-in testing cluster start up MemStore. But MemStore isn't based on database. So if we write complex query for some catalog method, MemStore would be difficult to adapt the query. So, we need to consider apply DerbyStore instead of MemStore for the testing cluster. I think it would be more useful compare than file based database using derby.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)