DirectQuery is more flexible than ever.
New DirectQuery Java API
The new DirectQuery Java API simplifies the process of creating applications from DirectQuery. It enables easier swapping between databases and offers greater commonality between connectors, such as a common schema description. This API enhances the development experience, providing you with more streamlined and efficient tools for your projects.
Experience this with all of our DirectQuery connectors: BigQuery, ClickHouse, Databricks, Dremio, MS SQL, Redshift, Snowflake, Synapse, and our generic JDBC connector. Our generic JDBC connector offers the flexibility to connect to a database not listed by specifying certain database specific details, like its SQL dialect. Notably, the Dremio connector is built using the generic JDBC connector, showcasing the versatility and extensibility of the generic JDBC connector. These connectors expand Atoti’s compatibility with various data sources, providing you with more integration options.
Aggregate Tables in DirectQuery
To further optimize database queries and reduce warehousing costs, Atoti now supports preaggregating tables in the data warehouse. These aggregate tables are used by DirectQuery to speed up queries, ensuring more efficient data retrieval and processing. This feature is especially useful when dealing with large-scale data warehouses, as it helps to minimize costs and improve performance.
Incremental Refresh
The incremental refresh capability in DirectQuery allows database updates to propagate to Atoti seamlessly. This ensures that data within Atoti remains up-to-date without the need for complete refreshes, improving efficiency and reducing the load on the database. Expect more timely and accurate data reflections within your Atoti environment.
Emulated Time Travel
DirectQuery used with a non-versioned database (no time travel) can have some de-synchronization issues. A de-synchronization issue is when there are data changes in the database that are not reflected in the Atoti server. Emulated time travel allows you to use version columns you have defined in the external database to avoid these issues.
Looking for more?
We hope you enjoyed this quick read. Looking for more content or news about this release or Atoti Server and Java API in general? Then check out our related blogs.
Don’t want to constantly check back for updates? We have you covered! Join the Atoti Community to receive these updates in a monthly digest!
