gianm commented on issue #19270: URL: https://github.com/apache/druid/issues/19270#issuecomment-4204169562
> An LLM found the following root cause for the issue The root cause sounds believable to me. I haven't verified it either, but, it's true that `canUseQueryGranularity` is meant to avoid situations where excessive granular buckets would be created. IMO the best fix would be to make it so the clipping happens on `unnest` datasources too, not just regular `table`. If that's not feasible, it would be ok to instead adjust `canUseQueryGranularity` to make the planner avoid granularity in this case. Since an LLM found the root cause, I wonder if the LLM can write a patch to fix it too 😄 -- 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]
