cleandataengineering.aiData Platform, from the big picture to the code
You are here: Start here › Code map › Who calls what › semantic

Data PlatformZoom level 3

Who calls what: semantic

Every class, function and method in the semantic package, with who calls it. Found by reading the code. A call written as object.method() is matched by the method's name, so a same-named method elsewhere can appear: those rows say by name.

35 definitions in 3 modules. Jump to a module: answers.py · experiences.py · metrics.py

semantic/answers.py

Ask a metric view's question of published gold (ADR-022 known answers, one number everywhere). Semantic layer

DefinitionWhat it does (its own first sentence)Called byNamed in tests
_where
function, line 20
question_sql · semantic/answers.py:31no test names it
question_sql
function, line 28
answers · semantic/answers.py:42no test names it
answers
function, line 36
{"<view>|<measure>|<oracle key>": the view's number} (the DP_GOLD_METRICS file's shape).gold_metrics · scripts/run_platform.py:293test_end_to_end.py, test_meta_store.py and 6 more

semantic/experiences.py

Dashboards and the conversation space, generated from the certified metric views (DPC-0076, SERV-04, SERV-06). Semantic layer

DefinitionWhat it does (its own first sentence)Called byNamed in tests
Tile
class, line 20
_page · semantic/experiences.py:61
module level · semantic/experiences.py:37 (value)
no test names it
Tile.title
method, line 27
_widget · realms/databricks/semantic_governance/render.py:197 (value)
dashboard_json · realms/databricks/semantic_governance/render.py:216 (value)
genie_space_json · realms/databricks/semantic_governance/render.py:252 (value)
_widget · adapters/lakeview.py:110 (value)
compile_dashboard · adapters/lakeview.py:136 (value)
test_genie_deploy.py, test_dac_coverage.py and 4 more
Page
class, line 34
_page · semantic/experiences.py:65
module level · semantic/experiences.py:45 (value)
no test names it
Dashboard
class, line 41
dashboards · semantic/experiences.py:75test_obs_dashboards.py
ConversationSpace
class, line 49
conversation_space · semantic/experiences.py:126no test names it
_page
function, line 58
dashboards · semantic/experiences.py:79no test names it
dashboards
function, line 68
One dashboard per domain, from certified views only (a preview view never reaches a dashboard).none found in the codetest_obs_dashboards.py, test_semantic_experiences.py and 2 more
_describe
function, line 85
sample_questions · semantic/experiences.py:95no test names it
sample_questions
function, line 89
A question per known answer (its exact address) and one per certified measure in its first synonym's words.conversation_space · semantic/experiences.py:131test_semantic_experiences.py
conversation_space
function, line 105
`views` are the published views; only the certified ones are attached. `all_views` (as read from the manifest, before publishing) supply the measures to decline.none found in the codetest_semantic_experiences.py

semantic/metrics.py

Metric views from the manifest's metric files (DPM v0.2 kind metric_view; ADR-022, DPC-0073, SERV-04, SERV-06). Semantic layer

DefinitionWhat it does (its own first sentence)Called byNamed in tests
MetricError
class, line 32
A metric file that cannot be read into a metric view.parse_where · semantic/metrics.py:108
metric_view · semantic/metrics.py:155
test_semantic_metrics.py
Dimension
class, line 37
_dimension · semantic/metrics.py:129
module level · semantic/metrics.py:83 (value)
_measure · semantic/metrics.py:132 (value)
no test names it
Filter
class, line 44
parse_where · semantic/metrics.py:115
module level · semantic/metrics.py:52 (value)
parse_where · semantic/metrics.py:101 (value)
no test names it
KnownAnswer
class, line 51
_measure · semantic/metrics.py:136no test names it
Measure
class, line 58
_measure · semantic/metrics.py:139
module level · semantic/metrics.py:84 (value)
test_obs_dashboards.py
Join
class, line 70
metric_view · semantic/metrics.py:165
module level · semantic/metrics.py:82 (value)
no test names it
MetricView
class, line 77
metric_view · semantic/metrics.py:168no test names it
MetricView.dimension
method, line 88
_where · realms/databricks/semantic_governance/render.py:131 (value)
_tile_query · realms/databricks/semantic_governance/render.py:169 (value)
_widget · realms/databricks/semantic_governance/render.py:191 (value)
scorecard · obs/success.py:157 (value)
_where · semantic/answers.py:21 (value)
_dimension · gold/harness.py:180 (by name)
and 1 more
test_semantic_governance.py, gold_helpers.py and 10 more
MetricView.certification
method, line 92
The lowest state of any measure the view exposes (the view's tag)._table_tags · governance/catalog.py:38 (value)
table_from_view · governance/tables.py:183 (value)
test_semantic_governance.py, test_governance_catalog.py and 2 more
parse_where
function, line 101
'region = 'south' AND promised month = 2026-11' -> filters on the view's dimensions (names ignore case)._measure · semantic/metrics.py:137test_semantic_metrics.py
_dimension
function, line 125
metric_view · semantic/metrics.py:167no test names it
_measure
function, line 132
metric_view · semantic/metrics.py:175no test names it
metric_view
function, line 151
One metric file -> a metric view. `gold` maps gold manifest names (facts and dimensions) to their documents; each join's key and schema come from there, so the metric file names a dimension and nothing more.build · realms/databricks/semantic_governance/generate.py:110
gold_metrics · scripts/run_platform.py:292
test_semantic_governance.py, test_governance_catalog.py and 2 more
lint
function, line 183
Problems that stop generation. Empty means every view may be published.build · realms/databricks/semantic_governance/generate.py:111no test names it
published
function, line 223
The views to create: the certified view under the manifest's name (only certified measures; what dashboards and the conversation interface read, SERV-06), and, if any measure is draft or reviewed, a _preview view with every measure that is build · realms/databricks/semantic_governance/generate.py:114
gold_metrics · scripts/run_platform.py:292
test_semantic_governance.py, test_gold_harness.py and 5 more
KnownAnswerCase
class, line 242
known_answer_cases · semantic/metrics.py:271
check_known_answers · semantic/metrics.py:287 (value)
test_semantic_metrics.py
KnownAnswerCase.label
method, line 249
known_answers_sql · realms/databricks/semantic_governance/render.py:144 (value)test_semantic_governance.py, test_semantic_metrics.py
KnownAnswerCase.oracle_key
method, line 253
The world oracle's address for this answer: the time value first, then the other filter values in order ('2026-11/south', '2026-11-12/P-CHN', '2026-11').oracle_value · semantic/metrics.py:280 (value)test_semantic_metrics.py
Verdict
class, line 262
check_known_answers · semantic/metrics.py:294test_silver_runner.py
known_answer_cases
function, line 268
Every certified measure's known answer, in view and measure order.generate · realms/databricks/semantic_governance/generate.py:166
gold_metrics · scripts/run_platform.py:293
sample_questions · semantic/experiences.py:93
test_semantic_metrics.py
oracle_value
function, line 278
Look a known answer up in the oracle's per-day metrics ({measure: {address: number | {expected: number}}}).none found in the codetest_semantic_metrics.py
check_known_answers
function, line 286
Ask `read` (a metric view, the oracle, a dashboard's dataset) each case; a missing value fails.none found in the codetest_semantic_metrics.py