You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Chandni Singh (JIRA)" <ji...@apache.org> on 2016/07/21 20:35:20 UTC

[jira] [Commented] (APEXCORE-448) Make operator name available in OperatorContext

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

Chandni Singh commented on APEXCORE-448:
----------------------------------------

Operator name is specified while adding an operator to the DAG. This name identifies the operator in the LogicalPlan so it cannot be changed later (cannot be changed using config file). This suggests that we should not  have a NAME attribute in OperatorContext because that will indicate that the Operator name can be changed through config. 

So this leads to having another method called `getName()` in OperatorContext.

[~pramod.immaneni] Can you please take a look?

> Make operator name available in OperatorContext
> -----------------------------------------------
>
>                 Key: APEXCORE-448
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-448
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Chandni Singh
>            Assignee: Chandni Singh
>
> Need name of the logical operator in the OperatorContext which can be used by WindowDataManager to create a unique path per logical operator .



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