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-496) Provide Operator name to StatsListener
Date Fri, 22 Jul 2016 06:41:20 GMT

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

ASF GitHub Bot commented on APEXCORE-496:
-----------------------------------------

GitHub user tushargosavi opened a pull request:

    https://github.com/apache/apex-core/pull/361

    APEXCORE-496 make operator name available to StatsListener.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tushargosavi/incubator-apex-core APEXCORE-496

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/apex-core/pull/361.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #361
    
----
commit 57bcad19ba9b2b94ac752a46bd7b6ef3b6ca2249
Author: Tushar R. Gosavi <tushar@apache.org>
Date:   2016-07-22T06:39:36Z

    APEXCORE-496 make operator name available to StatsListener.

----


> Provide Operator name to StatsListener
> --------------------------------------
>
>                 Key: APEXCORE-496
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-496
>             Project: Apache Apex Core
>          Issue Type: Task
>            Reporter: Tushar Gosavi
>            Assignee: Tushar Gosavi
>
> In case of shared statslistener it becomes difficult to identify for which operator
> s stats are being processed. we could provide operator name in BatchedOperatorStats to
easily identify the operator. 



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

Mime
View raw message