You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/21 05:12:44 UTC

[jira] [Commented] (APEXCORE-496) Provide Operator name to StatsListener

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

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

GitHub user tushargosavi opened a pull request:

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

    APEXCORE-496 Provide way for StatsListeners to get additional information

    

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

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

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

    https://github.com/apache/apex-core/pull/476.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 #476
    
----
commit 8663e443fc4e32639219a779a8444d9b4bec9e4a
Author: Tushar R. Gosavi <tu...@apache.org>
Date:   2017-02-21T02:57:02Z

    APEXCORE-496 Provide way for StatsListeners to get additional information.

----


> 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.15#6346)