XXXClientSettings(e.g.DatabricksClientSettings) configures how Atoti, acting as a client, interacts with the external database. The limits there apply in a general context (regular query, discovery query, time-travel discovery).XXXDatabaseSettings(e.g.DatabricksDatabaseSettings) configures how the Atoti cube (via its database object) interacts with the external database. Cube related limits are defined there, such as the feeding query timeout.
Summary
What is externalDatabaseQueryTimeout?
externalDatabaseQueryTimeout caps the duration of non-feeding queries.
A cube (MDX) query propagates its own timeout down to the database queries it triggers. The effective timeout for a database query is the minimum of the cube query’s own timeout and
externalDatabaseQueryTimeout.For example, if an MDX query is allowed 1 hour but externalDatabaseQueryTimeout is left at its 5-minute default, the generated database query still times out after 5 minutes. If your interactive queries legitimately need longer, raise both this limit and the MDX query timeout.- BigQuery
- ClickHouse
- Databricks
- Generic JDBC
- MS SQL
- Redshift
- Snowflake
- Synapse
What is feedingQueryTimeout?
feedingQueryTimeout applies to feeding queries: the queries run during the initial load to feed the aggregate providers and hierarchies, and during refresh operations.
- BigQuery
- ClickHouse
- Databricks
- Generic JDBC
- MS SQL
- Redshift
- Snowflake
- Synapse