Configurable query timeout based on group membership
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 49.3k
- Forks
- 6.8k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 653
Description
What problem will this feature request solve?
The customer set their database query timeout environment variable to 5 minutes to prevent non-technical folks from creating inefficient queries that slow down the whole organization. However, this causes a problem for the Data Analysts, who often write larger and more complex queries that often need more than 5 minutes to run. They currently use a different BI tool to run these larger queries.
Transforms and workspaces could potentially be a solution for them in the future (but they are not currently using transforms, hence this feature request).
Describe the solution you'd like.
Allow MB_DB_QUERY_TIMEOUT_MINUTES to be configurable by group.
How does this feature request impact you?
Would allow them to consolidate into one BI tool (Metabase) and have all of their reporting come from one place.
Additional information
Customer request
Related: https://github.com/metabase/metabase/issues/42677
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where MB_DB_QUERY_TIMEOUT_MINUTES is read and applied, then review related issue 42677 for existing context. Done means the query timeout can be configured by group membership while preserving the existing environment-variable behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100