[
https://issues.apache.org/jira/browse/APEXCORE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073507#comment-15073507
]
ASF GitHub Bot commented on APEXCORE-272:
-----------------------------------------
Github user tushargosavi commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/191#discussion_r48522048
--- Diff:
engine/src/main/java/com/datatorrent/stram/plan/logical/LogicalPlan.java ---
@@ -1359,7 +1409,8 @@ private void addDAGToCurrentDAG(ModuleMeta moduleMeta)
String name;
for (OperatorMeta operatorMeta : subDag.getAllOperators()) {
name = subDAGName + MODULE_NAMESPACE_SEPARATOR +
operatorMeta.getName();
- this.addOperator(name, operatorMeta.getOperator());
+ Operator op = this.addOperator(name, operatorMeta.getOperator());
--- End diff --
OperatorMeta has name and id declared as final field. In our case we want
to add the operator to top level dag with expanded name and wants to have a
unique id in the parent DAG. Hence reused the addOperator api without adding a
new one. This has additional cost of allocating new OperatorMeta though.
> Attributes added to operator inside Module is not preserved.
> ------------------------------------------------------------
>
> Key: APEXCORE-272
> URL: https://issues.apache.org/jira/browse/APEXCORE-272
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Tushar Gosavi
> Assignee: Tushar Gosavi
>
> Attributes added to operator within a Module is not preserved.
> for example
> {code}
> class M implements Module {
> public void populateDAG(DAG dag, Configuration conf) {
> DummyOperator o1 = dag.addOperator("O1", new DummyOperator());
> o1.setOperatorProp(level1ModuleProp);
> dag.getMeta(o1).getAttributes().put(Context.OperatorContext.MEMORY_MB,
> 512);
> }
> {code}
> The above code when module is expanded attribute set on operator o1 is lost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
