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

Posted to commits@oodt.apache.org by "Michael Starch (JIRA)" <ji...@apache.org> on 2015/04/28 19:32:06 UTC

[jira] [Resolved] (OODT-832) Move Streaming Components to Seperate Top-Level Component

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

Michael Starch resolved OODT-832.
---------------------------------
    Resolution: Fixed

With OODT-844 this work is done.

> Move Streaming Components to Seperate Top-Level Component
> ---------------------------------------------------------
>
>                 Key: OODT-832
>                 URL: https://issues.apache.org/jira/browse/OODT-832
>             Project: OODT
>          Issue Type: Sub-task
>          Components: resource manager
>    Affects Versions: 0.8, 0.8.1, 0.9
>            Reporter: Michael Starch
>             Fix For: 0.9
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Currently all of the streaming components are baked into their parent components. This forces new streaming technologies on unsuspecting users of the standard OODT deployment.
> These technologies should be moved to a separate top-level component, so that they are built separately, do not cause dependency hell, and can be included as optional add-ons to improve functionality of existing components.



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