[jira] [Updated] (APEXCORE-69) Improve StatsListener api so that using it with multiple logical operators is straightforward

["Chandni Singh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/APEXCORE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chandni Singh updated APEXCORE-69:
----------------------------------
    Assignee:     (was: Chandni Singh)

> Improve StatsListener api so that using it with multiple logical operators is straightforward
> ---------------------------------------------------------------------------------------------
>
>                 Key: APEXCORE-69
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-69
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Chandni Singh
>
> We have discussed theories about using a stats listener on multiple logical operators- specifically using stats from downstream operator to slow down upstream operator.
> While trying to implement such a StatsListener the processStats() methods becomes unwieldy which is mainly because there is no effortless way of knowing of which logical operator the stats are. BatchedOperatorStats contains operator id but that is assigned at the runtime (not known at the time of writing code).
> In past I have used counters to figure out the logical operator but that is a hack.



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