DirectQuery annotations

This section gives you an overview on how you can use the Spring annotations defined in Atoti Common Library to simplify the configuration when DirectQuery is used.

How it works

Some Spring annotations have been defined to make the definition of Beans easier. You can use these annotations at the Bean level or at the Class level.

Annotation	Description
@ConditionalOnInMemoryDatabase	This annotation is conditional on DirectQuery being disabled, that is, on the in-memory datastore being used. Underlying Spring property condition: - directquery.enabled=false
@ConditionalOnDirectQueryDatabase	This annotation is conditional on DirectQuery being enabled. Underlying Spring property condition: - directquery.enabled=true
@ConditionalOnClickhouse	This annotation is conditional on DirectQuery being enabled and configured to use a ClickHouse Database. Underlying Spring property condition: - directquery.enabled=true and directquery.database.type=clickhouse
@ConditionalOnDatabricks	This annotation is conditional on DirectQuery being enabled and configured to use a Databricks Database. Underlying Spring property condition: - directquery.enabled=true and directquery.database.type=databricks
@ConditionalOnMSSQL	This annotation is conditional on DirectQuery being enabled and configured to use a MSSQL Database. Underlying Spring property condition: - directquery.enabled=true and directquery.database.type=mssql
@ConditionalOnSnowflake	This annotation is conditional on DirectQuery being enabled and configured to use a Snowflake Database. Underlying Spring property condition: - directquery.enabled=true and directquery.database.type=snowflake