uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lou DeGenaro (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-3676) DUCC DB
Date Sun, 16 Mar 2014 12:58:42 GMT

    [ https://issues.apache.org/jira/browse/UIMA-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937119#comment-13937119
] 

Lou DeGenaro commented on UIMA-3676:
------------------------------------

Skeleton DB Component
1. DB Logger
2. DB Daemon JVM args
3. DB Daemon configuration class, publish endpoint, type and rate
4. Transport DB_DAEMON_STATE
5. Skeleton in uima-ducc-db
- DbComponent
- DbComponentCommonArea
- DbProperties
- DbComponentConfiguration (state publisher)
- DbComponentEventListener



> 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
>
> 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.2#6252)

Mime
View raw message