Re: Operator name in BatchedOperatorStats interface.

2016-08-08 Thread Tushar Gosavi
We will need more information about DAG in future for stats listener. I am planing to provide an interface between DAG and StatsListener to exchange more information. I have updated existing pull request to provide operator name from physical operator id through the new interface. https://github.c

Re: Operator name in BatchedOperatorStats interface.

2016-07-26 Thread Singh, Chandni
Hi, Please look at the following ticket: https://issues.apache.org/jira/browse/APEXCORE-448 If OperatorContext is provided in BatchedOperatorStats then it will solve this problem. Will propose the change on dev list and will create a pull request after that. Thanks, Chandni On 7/26/16, 10:5

Re: Operator name in BatchedOperatorStats interface.

2016-07-26 Thread Tushar Gosavi
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 wrote: > BatchedOperatorStats is implemented by the platform, adding a new method > returning the DAGContext should be fine. > > On Tue,

Re: Operator name in BatchedOperatorStats interface.

2016-07-26 Thread Sandesh Hegde
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 wrote: > Hi Sandesh, > > The StatsListner interface only has access to BatchedOperatorStats, > Changing the signature will be backward i

Re: Operator name in BatchedOperatorStats interface.

2016-07-26 Thread Tushar Gosavi
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 wrote: > How about making the mapping of "OperatorId" to "OperatorName" ( and other > extra inf

Re: Operator name in BatchedOperatorStats interface.

2016-07-25 Thread Sandesh Hegde
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 wrote: > Hi All, > > We support shared stats listener, But user do not have any way to > identify the operator for which th

Operator name in BatchedOperatorStats interface.

2016-07-18 Thread Tushar Gosavi
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