You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Lou DeGenaro (JIRA)" <de...@uima.apache.org> on 2015/08/28 15:18:45 UTC

[jira] [Resolved] (UIMA-3676) DUCC DB

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

Lou DeGenaro resolved UIMA-3676.
--------------------------------
    Resolution: Fixed

Expected use of traditional DB is abandoned in favor of OrientDB.

> DUCC DB
> -------
>
>                 Key: UIMA-3676
>                 URL: https://issues.apache.org/jira/browse/UIMA-3676
>             Project: UIMA
>          Issue Type: New Feature
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: future-DUCC
>
>
> DUCC currently used flat files of serialized Java objects to store history comprising Jobs, Reservations and Services.  And the WebServer currently caches only the most recent 4096 of each.
> Proposed is to explore the possibility of employing a DB, initially with Apache Derby, to better manage and utilize these potentially large historical data sets.  The DB would be owned by a new DUCC DB daemon and others such as Orchestrater, WebServer and Services Manager would interact with it to store, update and retrieve data.



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