Sound good, I will add one more interface to provide operator/dag level information to statslistener.
- Tushar. On Tue, Jul 26, 2016 at 8:37 PM, Sandesh Hegde <[email protected]> wrote: > BatchedOperatorStats is implemented by the platform, adding a new method > returning the DAGContext should be fine. > > On Tue, Jul 26, 2016 at 5:32 AM Tushar Gosavi <[email protected]> > wrote: > >> Hi Sandesh, >> >> The StatsListner interface only has access to BatchedOperatorStats, >> Changing the signature will be backward incompatible change. >> >> - Tushar. >> >> On Tue, Jul 26, 2016 at 12:09 AM, Sandesh Hegde <[email protected]> >> wrote: >> > How about making the mapping of "OperatorId" to "OperatorName" ( and >> other >> > extra information) as a part of the DAG context? >> > >> > >> > On Mon, Jul 18, 2016 at 10:53 PM Tushar Gosavi <[email protected]> >> > wrote: >> > >> >> Hi All, >> >> >> >> We support shared stats listener, But user do not have any way to >> >> identify the operator for which the stat listener is called. The >> >> BatchedOperatorStats only provides operatorId, and there is no api >> >> available to use to get operator information from operatorId. >> >> >> >> Can we include operator name as part of BatchedOperatorStats? This >> >> will allow users to take decision based on which operator stats are >> >> being processed. >> >> >> >> Regards, >> >> -Tushar. >> >> >>
