Re: [D] Add `verified_queries` as a core element of the spec [ossie]

["flyersworder (via GitHub)" <gi...@apache.org>]

GitHub user flyersworder added a comment to the discussion: Add `verified_queries` as a core element of the spec

Two notes from having shipped this.

**On Option A vs B** — we landed on neither. The corpus lives entirely outside the spec, and what our tooling contributes is *revalidation*: we take already-parsed `(question, sql)` records and re-run each one's SQL through the same validator that gates live agent queries, against the current contract. We never store, load, retrieve, or serve them.

That was a lifecycle decision, and it argues for B over A — a verified query goes stale when the *data* or the *policy* changes, not when the semantic model does, so embedding it in a metric couples two cadences that drift independently. But it also suggests the spec may not need to own the corpus at all, only to make it checkable.

**On @harelix's point** — agreed, and in practice the two aren't alternatives. Examples *ground*; they don't *enforce*. We carry structural requirements as first-class properties instead — a `required_filter` on a relationship, a priority-ordered `drill_by` on a metric — and validate SQL against those directly. If a required grouping is only implied by examples, a model will drop it under pressure; if it's a property, it's checkable.


GitHub link: https://github.com/apache/ossie/discussions/82#discussioncomment-18039052

----
This is an automatically sent email for dev@ossie.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@ossie.apache.org