The Horizon Catalog
The inventory, with keys and tags where the account grants them.
Read the Horizon Catalog into one governed layer
The Horizon Catalog is the catalogue. A semantic view is the contract you define once. Cortex Analyst is the question surface it feeds. Everything below came from probing a live account.
The header decides whether you are in
A programmatic access token sent with the OAuth header type is refused. The same token sent with the programmatic type works. That is the one tried first, the working header is remembered, and the connection test says which one answered.
- The wrong header returns an invalid token error, not a permission error
- Use the organisation and account host. The bare locator returns not found
- A not found on the SQL API reads as a wrong address. That one is often misread
Dimensions must name their entity
The same name is often defined on more than one entity, so a bare dimension name raises an ambiguity error. Names are qualified by entity, and a short name resolves only where it is unique.
- Contract members keyed by entity and name, never by name alone
- An ambiguous name is refused with the candidates listed
- The warehouse error text is shown word for word
Some entities are deliberately unrelated
Pair a dimension and a metric across two of them and Snowflake returns an error. That error is the model answering a question about itself.
- Errors shown word for word, never reworded
- Primary and foreign keys read as real column rules
- Tags read from account usage, best effort, with the lag named
What it reads
Semantic views
First-class objects, with their metric expressions and synonyms.
Governance
Key rules and tag lineage, inherited as they stand.