An analyst runs a query in Databricks SQL and receives results. She then modifies a filter condition and runs the query again within a few seconds. The second query returns results almost instantly. What feature is most likely responsible for this behavior?

Question

Accepted Answer

A. Query result cache. Databricks SQL automatically caches query results. When an identical or similar query is run again within the cache window, results are served from the cache rather than recomputing. Auto Loader is for data ingestion, not query acceleration. Z-ordering improves data layout for faster scans but does not serve cached results. Auto-scaling adds cluster nodes for concurrency, not repeated single-query acceleration.

An analyst runs a query in Databricks SQL and receives results. She then modifies a filter condition and runs the query again within a few seconds. The second query returns results almost instantly. What feature is most likely responsible for this behavior?

Related Questions

Discussion