TessaIO opened a new issue, #18840: URL: https://github.com/apache/druid/issues/18840
### Description Currently, when the query returned data is bigger than the max scatter-gather, we just log that the query's max scatter-gather bytes limit is reached, but we don't have visibility on how big is the data returned from the historical which makes Druid administration hard. ### Motivation We have some queries that are different in their nature and a max scatter-gather value can fit one query but not all. We want to this value on the context of the query so it's pretty customized. And for that, we need to know how much each query needed when it fails so we can adjust this value. -- 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]
