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 Thu, 04 Aug 2016 15:28:20 GMT

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

ASF GitHub Bot commented on APEXCORE-448:

Github user PramodSSImmaneni commented on the issue:

    I second it, please reopen this PR and I will merge it. I think we have spent enough time
on the tests and everyone's inputs have been valuable. There will be other opportunities in
future to add more tests and refactor them.
    My only small concern is adding a dependency to OperatorDeployInfo in OperatorContext,
can we completely justify that? I liked the earlier way where @chandnisingh was passing the
extra name as well, null check or without works for me.

> 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
> 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