Repository navigation
fix(examples): replace removed categories.primary with taxonomy.primary - #542
Conversation
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
🗺️ Overture Docs preview is live!
Note ♻️ This preview updates automatically with each push to this PR. |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Remaining current-release Snowflake, Athena, and Synapse examples still reference the removed categories field.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
What changed in this PR
Updates Places examples from removed categories.primary to taxonomy.primary for the 2026-09-23.0 release.
Changes:
- Updated three DuckDB queries.
- Updated the BigQuery example.
| File | Description |
|---|---|
src/queries/duckdb/seattle_places_for_map.sql |
Uses taxonomy.primary. |
src/queries/duckdb/places_wawa.sql |
Uses taxonomy.primary. |
src/queries/duckdb/new_york_pizza.sql |
Filters via taxonomy.primary. |
docs/getting-data/data-mirrors/bigquery.mdx |
Updates the BigQuery example. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
… Synapse examples
Alex Iannicelli (atiannicelli)
left a comment
There was a problem hiding this comment.
Categorically correct


The
2026-09-23.0release removed thecategoriesfield from places in favor oftaxonomy, so the DuckDB smoke tests started failing on every PR. This swapscategories.primaryfortaxonomy.primaryin the three example queries and the BigQuery snippet.Tested against live data from
2026-09-23.0.Closes #541.
Ref #539