ravisharm opened a new issue, #17171: URL: https://github.com/apache/druid/issues/17171
Often times question comes up on quantifying the cost of a query. Other products in similar domain e.g. AWS Redshift Serverless, Amazon Managed Service for Prometheus, Timestream etc. emit a metric that gives data scanned per query as a way to represent cost of the query. Druid needs to emit a similar metric. This issue proposes that metric to be number of rows scanned per query. [Query profile mechanism](https://github.com/apache/druid/issues/11800) also advocated Druid emitting metric on rows scanned. This metric can greatly help in determining costly queries and help understand how customers use Druid. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
