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] [Resolved] (APEXCORE-194) Add support for ProxyPorts in Modules
Date Tue, 22 Dec 2015 10:11:46 GMT

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

Tushar Gosavi resolved APEXCORE-194.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.3.0

Code for proxy port support is added through commit c1314ea

> Add support for ProxyPorts in Modules
> -------------------------------------
>
>                 Key: APEXCORE-194
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-194
>             Project: Apache Apex Core
>          Issue Type: Sub-task
>            Reporter: Bhupesh Chawda
>            Assignee: Bhupesh Chawda
>             Fix For: 3.3.0
>
>
> As part of supporting modules, we need some mechanism for mapping the module ports to
the operator ports. When an Apex application defines a DAG, the module is visible only as
a black box, until the populateDag() method of that module is called. Till that time, only
the module's ports are exposed and streams are created based on the module's ports. The ports
of the operators within the module are hidden till that time. Now, when the DAG is expanded,
the operators inside the module get exposed and we can know what are the correct end points
for the streams that were defined earlier.



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

Mime
View raw message