Release Date: 2026-06-03
New Feature: MaxQA (MCQA V2) Interactive Query Acceleration
MaxQA is MaxCompute's next-generation interactive query acceleration engine. Queries that take 30+ seconds in offline mode can often complete in under 5 seconds with MaxQA.
Profile Configuration
my_profile:
target: dev
outputs:
dev:
type: maxcompute
project: my_project
schema: default
endpoint: http://service.cn-hangzhou.maxcompute.aliyun.com/api
access_key_id: "{{ env_var('ODPS_ACCESS_ID') }}"
access_key_secret: "{{ env_var('ODPS_SECRET_ACCESS_KEY') }}"
execution_mode: maxqa
quota_name: my_interactive_quota # optionalNew Profile Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
execution_mode |
String | "offline" |
"offline" uses standard batch engine; "maxqa" routes queries through MaxQA |
quota_name |
String | - | Interactive quota group name (optional) |
maxqa_fallback |
Boolean | true |
Enable server-side fallback to offline for unsupported queries (e.g. DDL) |
maxqa_fallback_quota |
String | - | Offline quota group name used for fallback |
Per-Model Override
Override execution mode on individual models via sql_hints:
-- Force offline for a heavy model
{{ config(materialized='table', sql_hints={'dbt.execution_mode': 'offline'}) }}
-- Use MaxQA for a specific model
{{ config(materialized='table', sql_hints={'dbt.execution_mode': 'maxqa', 'dbt.quota_name': 'my_quota'}) }}dbt.execution_mode and dbt.quota_name are consumed by the adapter and never sent to MaxCompute.
Fallback Behavior
| Setting | Behavior |
|---|---|
maxqa_fallback: true (default) |
Server automatically falls back to offline for unsupported queries |
maxqa_fallback: false |
No fallback — unsupported queries will fail |
maxqa_fallback_quota: my_offline_quota |
Falls back to a specific offline quota group |
Bug Fixes
- Ephemeral test assertions updated for dbt-core 1.11.7's switch from
CREATE VIEWtoCREATE OR REPLACE VIEW