[
https://issues.apache.org/jira/browse/APEXCORE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257255#comment-15257255
]
ASF GitHub Bot commented on APEXCORE-107:
-----------------------------------------
Github user PramodSSImmaneni commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/313#issuecomment-214563277
In the current form, where module gets materialized in the logical plan and
does not have a runtime aspect to itself directly, it would be difficult to
justify/attribute the lifecycle methods to the module. Maybe module and
operator can inherit from a common element which could be the building block of
DAG. Thats a bigger change and requires more discussions with wider group.
> Support adding module to application using property file API.
> -------------------------------------------------------------
>
> Key: APEXCORE-107
> URL: https://issues.apache.org/jira/browse/APEXCORE-107
> Project: Apache Apex Core
> Issue Type: Task
> Reporter: Tushar Gosavi
> Assignee: Tushar Gosavi
>
> Add support for adding modules in the DAG specified through property file and
> json file. The sample json format is specified below.
> {code}
> {
> "operators": [
> {
> "name": "operator1",
> "class": "com.datatorrent.lib.operator.Input",
> "properties": {
> "property1": "value1"
> }
> },
> {
> "name": "module1",
> "class": "com.datatorrent.module.Module1",
> "properties": {
> "property1": "value1"
> }
> },
> ],
> "streams": [
> {
> "name": "s1",
> "source": {
> "operatorName": "operator1",
> "portName": "output"
> },
> "sinks": [
> {
> "operatorName": "module",
> "portName": "input"
> }
> ]
> }
> ]
> }
> {code}
> For this to work, we will need to support adding module in DAG through
> property file API.
> This will allow external tools to visually construct the DAG containing
> modules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
