[
https://issues.apache.org/jira/browse/OODT-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219313#comment-13219313
]
Sheryl John commented on OODT-212:
----------------------------------
Almost, but I thought in terms of rolling back to a task instance.Maybe a bad
idea, since I was thinking in terms of tasks with states or flags. So the
workflow processor/instance will have the list of all tasks instances ( with
success flags) assigned to it. And if we detect #TaskSuccessFlag set as 0 in
the workflow-context metadata, then the processor could revert back to a
previous successful task instance.
When you meant "transition into a state that's "roll back-able"", would that
also give you the task instance to roll back from?
The 'least dramatic' steps was how I saw you could do this.
> Rollback capability for Workflows
> ---------------------------------
>
> Key: OODT-212
> URL: https://issues.apache.org/jira/browse/OODT-212
> Project: OODT
> Issue Type: Sub-task
> Components: workflow manager
> Environment: From JPL's internal JIRA, pre-Apache
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 0.4
>
>
> Since workflows can involve sequences of PGE-type tasks that can possibly
> fail, and whose failure may invalidate subsequent PGEs that have already been
> processed, it might be good to have a capability for rolling back
> interactions from prior tasks in a workflow. This is a placeholder for future
> patches on that issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
