-
Notifications
You must be signed in to change notification settings - Fork 337
Team query timeout setting #1072
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🦋 Changeset detectedLatest commit: be1620b The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Bit difficult to trace all usages of the client, let me know if I wrote anything crazy here 👀 |
Stably Runner - Test Suite - 'Smoke Test'Test Suite Run Result: 🟢 Success (4/4 tests passed) [dashboard] This comment was generated from stably-runner-action |
teeohhem
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…cer/feat_team_query_timeout
|
Perhaps those queries without the timeout were the metadata queries? I added the timeout to the metadata queries, it looks like those are cached and simply fetch the tables, so I kept the 60s default on those. Not sure if we care to apply the team configured timeout to those, but now they have some timeout in case they run long (I don't expect they will) |
…cer/feat_team_query_timeout
teeohhem
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
…cer/feat_team_query_timeout
…cer/feat_team_query_timeout
For example, it defaults to 60 seconds, but a timeout gets created for 60 milliseconds. ## Before <img width="2850" height="1264" alt="Screenshot 2025-11-28 at 2 11 33 PM" src="https://github.com/user-attachments/assets/8eff105b-39b0-459b-bdf3-a149645e3c57" /> ## After <img width="1848" height="1086" alt="Screenshot 2025-11-28 at 2 19 20 PM" src="https://github.com/user-attachments/assets/406f53ed-cda0-4ccc-9442-249d6a507a5a" /> Original PR: #1072 Bug Introduced here: #1132 Closes #1416 Fixes HDX-2931

Closes HDX-2023
Behavior
Adds
queryTimeoutto the team settings page. If the setting is greater than0, amax_execution_timesetting is added to all queries executed by theClickhouseClient. The timeout is in seconds, with60seconds being the default.0would be unlimited.Images
Settings page:

Network log:
