Re: Setting the operator-id to measure percentile latency over several jobs

I talked to Chesnay about this offline. Shipping the operator names with the latency markers would significantly increase their size (potentially affecting performance) There is no global lookup from operatorId to operatorName. On Fri, Mar 6, 2020 at 5:34 PM Robert Metzger wrote: > @Chesnay Sche

Re: Setting the operator-id to measure percentile latency over several jobs

@Chesnay Schepler : Does it make sense to file a ticket to add the operator name to the latency metrics as well? On Thu, Mar 5, 2020 at 4:31 PM Felipe Gutierrez < felipe.o.gutier...@gmail.com> wrote: > thanks! I was wondering why the operator name is not implemented for the > latency metrics, bec

Re: Setting the operator-id to measure percentile latency over several jobs

thanks! I was wondering why the operator name is not implemented for the latency metrics, because for the other metrics it is implemented. but thanks anyway! *--* *-- Felipe Gutierrez* *-- skype: felipe.o.gutierrez* *--* *https://felipeogutierrez.blogspot.com

Re: Setting the operator-id to measure percentile latency over several jobs

Hi Felipe, Please find the answers to your questions below. > Each "operator_subtask_index" means each instance of the parallel physical operator, doesn't it? Yes. > How can I set a fixed ID for the "operator_id" in my code so I can identify quickly which operator I am measuring? You are using th