gianm commented on issue #7957: Druid SQL planning time can exceed query timeouts URL: https://github.com/apache/incubator-druid/issues/7957#issuecomment-505497428 Timeouts are checked at various points in the query lifecycle (not continuously) so it does make sense that this can happen. Currently, the main points they're checked are: - On historicals during query processing, depending on query engine and algorithm used, either between every row or between every segment - On the broker, when it's reading data from historicals Might be nice to add timeout checking in a few more places. However, for the specific issue in #7904, it probably wouldn't be interruptible since it's spinning inside Calcite code on something algorithmically excessive. That algorithmic excessiveness should just be fixed in Calcite itself and then the newer version of Calcite pulled into 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
