apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vlad Rozov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-587) Allow access to DAG through the Launcher API
Date Thu, 08 Dec 2016 02:42:58 GMT

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

Vlad Rozov commented on APEXCORE-587:

I agree, it should be OK to move getDAG() to the application handle returned by the launchApp()
API. It may be possible to use prepareDAG() to get newly created DAG, but it does need to
support preparing more than one DAG/Application. I would also consider using a different class
to provide such functionality in case DAG creation/preparing does not depend on the Launcher
implementation. Currently, there is only one class that implements DAG, and delegating DAG
creation to different Launcher implementations is not necessary.

> Allow access to DAG through the Launcher API
> --------------------------------------------
>                 Key: APEXCORE-587
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-587
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Thomas Weise
>            Priority: Minor
> It is useful for clients to access the DAG without launching it. The existing methods
from EmbeddedLauncher (getDAG, prepareDAG) should be available through the parent class.

This message was sent by Atlassian JIRA

View raw message