[GH-ISSUE #2606] Enhancement Request: Clarification and Consistency of sqlQueryTimeout Behavior #871

New issue

Open

opened 2026-03-07 20:56:02 +03:00 by kerem · 0 comments

kerem commented

2026-03-07 20:56:02 +03:00

Owner

Originally created by @matthieukhl on GitHub (May 13, 2024).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/2606

Currently, there appears to be confusion regarding the behavior of the sqlQueryTimeout configuration parameter in CloudBeaver. The documentation states that it sets the maximum time (in seconds) for SQL query execution, including table data read. However, according to recent discussions and testing, it seems that this setting only affects the SQL editor and does not enforce query execution time limits for other components, such as JDBC drivers interacting with databases like MySQL, TiDB, or ClickHouse.

It is essential to clarify and ensure consistency in the behavior of sqlQueryTimeout across all relevant components within CloudBeaver. This enhancement request proposes the following actions:

Documentation Update: Update the documentation to accurately reflect the behavior of sqlQueryTimeout, specifying its scope and limitations. Clearly indicate which components and scenarios are affected by this setting.
Feature Enhancement: Extend the functionality of sqlQueryTimeout to enforce query execution time limits consistently across all database interactions, including JDBC drivers.

By addressing these points, CloudBeaver can offer users a more transparent and reliable experience when configuring and managing query execution time limits. This enhancement aligns with the goal of providing robust database management solutions that meet the diverse needs of users.

Thank you for considering this enhancement request.

Originally created by @matthieukhl on GitHub (May 13, 2024). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/2606 Currently, there appears to be confusion regarding the behavior of the **sqlQueryTimeout** configuration parameter in CloudBeaver. The documentation states that it sets the maximum time (in seconds) for SQL query execution, including table data read. However, according to recent discussions and testing, it seems that this setting only affects the SQL editor and does not enforce query execution time limits for other components, such as JDBC drivers interacting with databases like MySQL, TiDB, or ClickHouse. It is essential to clarify and ensure consistency in the behavior of sqlQueryTimeout across all relevant components within CloudBeaver. This enhancement request proposes the following actions: - **[Documentation Update](https://github.com/dbeaver/cloudbeaver/wiki/Server-configuration#resource-quotas)**: Update the documentation to accurately reflect the behavior of sqlQueryTimeout, specifying its scope and limitations. Clearly indicate which components and scenarios are affected by this setting. - **Feature Enhancement**: Extend the functionality of sqlQueryTimeout to enforce query execution time limits consistently across all database interactions, including JDBC drivers. By addressing these points, CloudBeaver can offer users a more transparent and reliable experience when configuring and managing query execution time limits. This enhancement aligns with the goal of providing robust database management solutions that meet the diverse needs of users. Thank you for considering this enhancement request.