[
https://issues.apache.org/jira/browse/APEXCORE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15610156#comment-15610156
]
Thomas Weise commented on APEXCORE-560:
---------------------------------------
It depends on the use case. As suggested earlier, there may be cases where the
user wants to add back the same operator with different configuration and there
may be cases where a part of the DAG isn't known beforehand. I could think of
someone adding an operator for diagnosis purposes and removing it later, for
example. Given that we already have support for add and remove, we should fix
the remove. Activate/deactivate is a new functionality that should be taken up
separately. It may be better suited for the batch case we discussed, at the
same time the batch use case can be done without it also, it's a compromise.
> Logical plan is not changed when all physical partitions of operator are
> removed from DAG
> -----------------------------------------------------------------------------------------
>
> Key: APEXCORE-560
> URL: https://issues.apache.org/jira/browse/APEXCORE-560
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Bhupesh Chawda
>
> Throwing a ShutdownException() from an input operator removes them from the
> physical plan, but can still be seen in the logical plan. Ideally the
> corresponding logical operator must also be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
