You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ossie.apache.org by "djwaldo (via GitHub)" <gi...@apache.org> on 2026/07/30 02:32:10 UTC
Re: [D] Semantic Filters [ossie]
GitHub user djwaldo added a comment to the discussion: Semantic Filters
Reviving this with data from the ThoughtSpot converter mapping (#285). The expression-language doc already assumes filters exist twice. It scopes itself to "metrics, fields, filters, etc" and redirects WHERE to "the filter property". But the core schema defines no such property. In practice every vendor has one (ThoughtSpot has model filters and join constraints; the Databricks Metric View has filter) and every converter is stashing it in custom_extensions today. A stashed filter is invisible to other consumers, which means the same semantic model returns different numbers in two tools — of everything we mapped, this is the highest-value gap in the core spec.
Proposal: a minimal core filters construct (column, operator, values) at semantic-model and/or dataset scope, with anything fancier staying vendor-extension.
GitHub link: https://github.com/apache/ossie/discussions/5#discussioncomment-17834470
----
This is an automatically sent email for dev@ossie.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@ossie.apache.org