[jira] [Commented] (OODT-263) Resource Manager needs to support flexible JobOutput formats

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

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

Chris A. Mattmann commented on OODT-263:
----------------------------------------

I need to think about this one some more. I think that I might be able to solve the aforementioned problem for the workflow manager inside of the workflow mgr itself. However, I am going to leave this issue open and reported though, because I think it makes sense and we're going to need to deal with it. However, for now, I think we can table it and just deal with the problem in the workflow manager.

> Resource Manager needs to support flexible JobOutput formats
> ------------------------------------------------------------
>
>                 Key: OODT-263
>                 URL: https://issues.apache.org/jira/browse/OODT-263
>             Project: OODT
>          Issue Type: New Feature
>          Components: resource manager
>         Environment: JPL internal JIRA
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> One of the things that was never implemented in the resource manager is the return of a resource manager Job's Output in a flexible format (e.g., different Job's should be able to return different JobOutputs). This particular feature is important, say in the case where the WorkflowTasks within a Workflow depend on their shared Metadata context being updated and still fresh, even though the WorkflowTask's are now distributed, and not run on a single host anymore.
> Prior to the resource manager, since all Workflow's were run on a single host (in a multi-threaded fashion, but still on a single host), the Metadata context shared between WorkflowTasks was always updated and kept fresh because all WorkflowTasks had access to it, because all WorkflowTasks were running in the same Java Virtual Machine. Now with the WorkflowTask's being distributed, when a distributed WorkflowTask updates its Metadata context, those changes need to be propagated back to the Workflow manager so that it can allow other subsequent WorkflowTasks to use the (possibly) new values within the Metadata.
> This patch will define a JobOutput interface, and make an instance of that interface the return value from the execution of a Resource Manager job. Another, separate, patch will provide a WorkflowJobOutput class for the Workflow manager, so that it can obtain the property output from its WorkflowTasks.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira