You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2021/10/21 17:01:04 UTC

[GitHub] [pinot] richardstartin commented on issue #7611: Query trace info for a large table and cluster is not readable

richardstartin commented on issue #7611:
URL: https://github.com/apache/pinot/issues/7611#issuecomment-948811255


   The purpose of tracing is to record a trace of what happened, rolling the trace up would disguise what happened. I think the real problem is one of presentation. E.g. exporting operator invocations as JFR events.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org