Routing Queries To Analytical Views Defined on Tables

In the presence of a relevant analytical view, the user query is diverted from hitting base tables and instead computes based on data cached in the analytical view.
Query Routing Through Arcadia's Analytical Views

Routing enables Arcadia Engine to transparently use the data from an analytical view, instead of having the query processed on the base tables. The engine routes the input query from the user (QI) to an analytical view by matching QI to a query that was earlier used to define the analytical view (QA). It then substitutes parts (or all) of QI by QA. If a matching analytical view is not found, the query is evaluated against the base table.

It is possible to benefit from incremental refresh (which ensures faster loading of data into analytical view) if the analytical view is partitioned on the same column(s) as the table.

Some limitations of defining analytical views on base tables are that analytical views cannot model joins, sub-queries, window functions, and unions. This limits the SQL expressions that can be supported by analytical views to single table domains. Contrast this with Routing Queries with Logical Views to Analytical Views, which supports joins, sub-queries, window functions, unions, and all other SQL operations.

Also note that Arcadia Engine recognizes changes to base tables in Hive. If these changes are disruptive, Arcadia Engine marks the dependent analytical views as INVALID.