apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tushar Gosavi <tus...@datatorrent.com>
Subject Re: Operator name in BatchedOperatorStats interface.
Date Mon, 08 Aug 2016 18:56:39 GMT
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.com/apache/apex-core/pull/361

Regards,
-Tushar.

On Wed, Jul 27, 2016 at 12:09 AM, Singh, Chandni
<Chandni.Singh@capitalone.com> wrote:
> 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:53 AM, "Tushar Gosavi" <tushar@datatorrent.com> wrote:
>
>>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 <sandesh@datatorrent.com>
>>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 <tushar@datatorrent.com>
>>> 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
>>>><sandesh@datatorrent.com>
>>>> 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
>>>><tushar@datatorrent.com>
>>>> > 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.
>>>> >>
>>>>
>>
>
> ________________________________________________________
>
> The information contained in this e-mail is confidential and/or proprietary to Capital
One and/or its affiliates and may only be used solely in performance of work or services for
Capital One. The information transmitted herewith is intended only for use by the individual
or entity to which it is addressed. If the reader of this message is not the intended recipient,
you are hereby notified that any review, retransmission, dissemination, distribution, copying
or other use of, or taking of any action in reliance upon this information is strictly prohibited.
If you have received this communication in error, please contact the sender and delete the
material from your computer.
>

Mime
View raw message