apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tushar Gosavi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-408) Ability to schedule Sub-DAG from running application
Date Thu, 06 Apr 2017 12:59:41 GMT

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

Tushar Gosavi commented on APEXCORE-408:
----------------------------------------

[~thw] I have opened a pull request https://github.com/apache/apex-core/pull/476 for statslistener
 changes. I am implementing the second approach from the document as it would be simple and
won't change existing code much. There are few problems I am facing regarding the validation
done by LogicalPlan while elements are being added to it, like extending a stream the port
needs to be present in the DAG. When I try to extend an existing stream with new operator's
input port , as new operator's input port is not in the original DAG , it throws as error
as port does not belong to any operator in the DAG. Trying to solve this problem.

> Ability to schedule Sub-DAG from running application
> ----------------------------------------------------
>
>                 Key: APEXCORE-408
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-408
>             Project: Apache Apex Core
>          Issue Type: Sub-task
>            Reporter: Thomas Weise
>            Assignee: Tushar Gosavi
>
> Today it is possible to add operators to a running application from the CLI/client. It
should be possible to do this from within the application also. This can be used to expand/remove
a Sub-DAG on demand, triggered by application specific logic. It will enable use cases such
as batch applications that perform multiple stages of processing where not all resources are
required at the same time or the logic of subsequent steps depends on the execution of previous
steps.    



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message