alamb closed issue #16044: Support distribution as a MetricValue in
ExecutionPlan
URL: https://github.com/apache/datafusion/issues/16044
--
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
sfluor commented on issue #16044:
URL: https://github.com/apache/datafusion/issues/16044#issuecomment-2912336910
/take
--
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 un
sfluor commented on issue #16044:
URL: https://github.com/apache/datafusion/issues/16044#issuecomment-2912341485
take
--
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 uns
sfluor commented on issue #16044:
URL: https://github.com/apache/datafusion/issues/16044#issuecomment-2912337792
Here's the PR @gabotechs [feat: Support defining custom MetricValues in
PhysicalPlans](https://github.com/apache/datafusion/pull/16195#top) with an
example of how to use this new
gabotechs commented on issue #16044:
URL: https://github.com/apache/datafusion/issues/16044#issuecomment-2910200484
👍 This sounds very reasonable, it would be interesting to know what are the
stance of DF maintainers on what is considered too coupled to a specific use
case vs what is reason
gabotechs commented on issue #16044:
URL: https://github.com/apache/datafusion/issues/16044#issuecomment-2910201827
In your example, what would `TDigest` look like?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
sfluor opened a new issue, #16044:
URL: https://github.com/apache/datafusion/issues/16044
### Is your feature request related to a problem or challenge?
The MetricValue enum currently exposes only single-value statistics: counts,
gauges, timers, timestamps, and a few hard-coded varian
