Quick answer
Semantic inheritance copies a bounded metadata projection from an upstream catalog into Amazon Quick representations. The catalog remains authoritative; generated Datasets keep inherited definitions read-only and expose a manual Sync semantics action.
Current inheritance is not the entire catalog record:
- table and column descriptions flow into Datasets;
- primary and foreign key definitions inform relationships and Topics;
- discovery can use broader metadata such as quality signals or tags without inheriting all of it;
- support for additional semantic information is described as future work.
Treat sync as a reviewed metadata deployment, not as proof that a definition or relationship is correct.
Source-of-truth model
| Layer | Ownership |
|---|---|
| Upstream catalog | Approved definitions, descriptions, relationships, ownership, and governance metadata |
| Quick generated Dataset | Read-only representation of inherited table and column semantics |
| Quick Topic | Reviewed relationship and context boundary across selected Datasets |
| Custom Quick Dataset | Quick-owned edits or transformations; no further semantic sync |
Quick is documented as a consumer of catalog metadata, not a dedicated replacement catalog. Correct errors upstream when possible so all consumers receive the fix.
Manual sync workflow
Before choosing Sync semantics:
- identify upstream definition and relationship changes;
- review the catalog change owner and approval;
- assess affected Datasets, Topics, dashboards, Q&A, and users;
- capture baseline questions and known totals;
- sync in a controlled environment;
- inspect definition and relationship changes;
- rerun regression questions and permission tests;
- promote or roll back through the normal governance process.
AWS’s launch post describes scheduled automatic sync as roadmap. Do not promise a schedule unless current product documentation confirms it.
Dataset customization is a fork
Authors can switch a generated Dataset to SPICE or add transformations. AWS states that semantic sync then stops and the asset becomes a standard Quick Dataset.
That also affects governance: identity propagation works only for DirectQuery and no longer applies after SPICE or transformations. Before customizing, decide who owns definitions, access controls, refresh, transformations, lineage, and drift detection in the fork.
Use the identity propagation guide for the permission consequence and the Datasets and Topics guide for asset behavior.
Detect semantic drift
Track catalog and Quick representation versions. Monitor:
- changed metric wording or business terms;
- renamed, added, or removed columns;
- key and cardinality changes;
- owner, sensitivity, or quality changes;
- Dataset forks that no longer sync;
- Topics using stale relationships;
- dashboard or Q&A regressions after a sync.
Do not use a “Semantics inherited” badge as a freshness guarantee. Record the last successful review and sync evidence.
Review AI recommendations
The Agent can recommend tables and infer relationships, but authors must review them. Distinguish:
- inherited fact: metadata read from the upstream catalog;
- agent inference: a proposed relationship or relevance judgment;
- author approval: a human governance decision;
- validated behavior: reconciled queries and permission tests.
Only the last two support a controlled rollout.
Frequently asked questions
What metadata does Amazon Quick inherit from catalogs?
Current preview documentation says generated Datasets inherit table and column descriptions, while Topics can use primary and foreign key relationship definitions. Additional semantic types are not all inherited.
Is semantic sync automatic?
The documented current control is manual: an author chooses Sync semantics. AWS lists scheduled automatic sync as roadmap in the launch post.
What happens if I edit a generated Dataset?
Adding transformations or switching to SPICE makes it a standard Quick Dataset; semantic sync is no longer available, and DirectQuery-only identity propagation no longer applies.
Official sources
- Amazon Quick: Behavior of created datasets
- Amazon Quick: The agentic catalog experience
- AWS launch post: Agentic Catalog Experience
Source check: August 4, 2026. Verify preview behavior, inheritance scope, sync controls, and customization consequences before use.