You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running complex queries over large haystacks, a way to bound the query execution time with proper cancellation propagation to datafusion would be useful.
Based on my (cursory and AI-assisted) reading of the code, since datafusion already uses Tokio's cooperative task scheduling system, wrapping the query execution in a tokio::time::timeout(...) should work. Happy to contribute a PR for this or other ideas that would allow a bounded query time.
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon May 5, 2026
🔗 Related PRs
#1393 - Update mod.rs [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
nikhilsinhaparseable commentedon May 5, 2026
@shikharbhardwaj you can work on it and send the PR, will be glad to review the PR
nitisht commentedon Jun 17, 2026
Fixed by #1683