atoti_directquery_databricks.ConnectionConfig(Config to connect to a Databricks database.
*,
password: str | None =None,
auto_multi_column_array_conversion: AutoMultiColumnArrayConversion | None =None,
column_clustered_queries: ‘all’ | ‘feeding’ ='feeding',
feeding_query_timeout: Duration =datetime.timedelta(seconds=3600),
lookup_mode: ‘allow’ | ‘warn’ | ‘deny’ ='warn',
max_sub_queries: Annotated[int, Field(gt=0)] =500,
query_timeout: Duration =datetime.timedelta(seconds=300),
url: str,
feeding_url: str | None =None,
time_travel: Literal[False, ‘lax’, ‘strict’] ='strict',
)
Attributes
url
The JDBC connection string.feeding_url
When notNone, this JDBC connection string will be used instead of url for the feeding phases.
time_travel
How to use Databricks’ time travel feature. Databricks does not support time travel with views, so the options are:False: tables and views are queried on the latest state of the database."lax": tables are queried with time travel but views are queried without it."strict": tables are queried with time travel and querying a view raises an error.
auto_multi_column_array_conversion
When notNone, multi-column array conversion will be performed automatically.
column_clustered_queries
Control which queries will use clustering columns.feeding_query_timeout
Timeout for queries performed on the external database during feeding phases. The feeding phases are:- the initial load to feed
aggregate_providersandhierarchies; - the refresh operations.
lookup_mode
Whether lookup queries on the external database are allowed. Lookup can be very slow and expensive as the database may not enforce primary keys.max_sub_queries
Maximum number of sub queries performed when splitting a query into multi-step queries.password
The password to connect to the database. Passing it in this separate attribute prevents it from being logged alongside the connection string. IfNone, a password is expected to be present in url.