apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-448) Make operator name available in OperatorContext
Date Wed, 03 Aug 2016 21:42:20 GMT

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

ASF GitHub Bot commented on APEXCORE-448:

Github user vrozov commented on a diff in the pull request:

    --- Diff: engine/src/main/java/com/datatorrent/stram/engine/OperatorContext.java ---
    @@ -84,12 +87,13 @@ public void setIdleTimeout(long idleTimeout)
        * @param attributes the value of attributes
        * @param parentContext
    -  public OperatorContext(int id, AttributeMap attributes, Context parentContext)
    +  public OperatorContext(int id, String operatorName, AttributeMap attributes, Context
    --- End diff --
    id, name and attributes are public fields on OperatorDeployInfo. Using OperatorDeployInfo
will allow avoiding changes to the OperatorContext constructor each time a new field is introduced.
There seems to be the dependency in production code between OperatorContext and OperatorDeployInfo

> 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

View raw message