Title: feat: Support Feast DQM for Chronon outputs with freshness and lineage context · Issue #6984 · feast-dev/feast · GitHub
Open Graph Title: feat: Support Feast DQM for Chronon outputs with freshness and lineage context · Issue #6984 · feast-dev/feast
X Title: feat: Support Feast DQM for Chronon outputs with freshness and lineage context · Issue #6984 · feast-dev/feast
Description: Problem Teams should be able to inspect Chronon feature quality in their existing Feast project. Our working demonstration currently profiles an exported checkout snapshot using a separate Dask/FileSource setup. That export's timestamp d...
Open Graph Description: Problem Teams should be able to inspect Chronon feature quality in their existing Feast project. Our working demonstration currently profiles an exported checkout snapshot using a separate Dask/Fil...
X Description: Problem Teams should be able to inspect Chronon feature quality in their existing Feast project. Our working demonstration currently profiles an exported checkout snapshot using a separate Dask/Fil...
Opengraph URL: https://github.com/feast-dev/feast/issues/6984
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feat: Support Feast DQM for Chronon outputs with freshness and lineage context","articleBody":"## Problem\n\nTeams should be able to inspect Chronon feature quality in their existing Feast project. Our working demonstration currently profiles an exported checkout snapshot using a separate Dask/FileSource setup. That export's timestamp describes the snapshot, not freshness of Chronon's source data or serving pipeline.\n\nThe Chronon adapter can already read published Parquet for profiling, and Feast has a Python metric-computation fallback. The missing integration includes persistent monitoring storage: the adapter does not implement the monitoring storage hooks expected by `MonitoringService`. Online reads also currently return no feature timestamp, so they cannot establish source freshness.\n\n## Proposed solution\n\nStart with persisted DQM over Chronon batch outputs in a Chronon-configured Feast repository:\n\n- Implement the required metrics, baseline, and monitoring-job persistence, either through the adapter or an explicitly configured metrics backend.\n- Reuse the existing Feast monitoring API/UI for profiles and historical date buckets.\n- Associate monitored outputs with the Feast FeatureView and Chronon GroupBy/Join, plus output version or pipeline run when available.\n- Keep event time, feature-computation time, export time, and metric-computation time distinct. Missing timestamp or provenance metadata should remain unknown.\n\nContinuous serving-log ingestion and online/offline consistency checks should have separate follow-ups unless explicitly implemented here. Output profiling alone does not establish those properties.\n\n## Acceptance criteria\n\n- [ ] One Chronon-configured repository computes and displays profiles, baselines, and multiple date buckets through the existing REST API/UI, without duplicating definitions in a separate Dask/FileSource repository.\n- [ ] Metrics and job state survive restart, retries do not create duplicate metrics, and baseline replacement works.\n- [ ] Integration fixtures verify null preservation, mapped feature names, entity keys, timestamp filtering, and known metric values.\n- [ ] A stale-output fixture with a recent export is not reported as source-fresh. Absent timestamp/run metadata has an explicit unknown state.\n- [ ] API/UI metadata lets users trace a monitored feature to its Chronon definition and available output provenance.\n- [ ] Documentation and a runnable example explain supported storage, permissions, date semantics, and the distinction between output quality, pipeline freshness, and online/offline consistency.\n\n## Alternatives considered\n\nContinue exporting snapshots into a separate monitoring repository, or use an external quality tool. A configurable metrics backend may be preferable to forcing monitoring writes into Chronon's feature storage; evaluate that choice in the design.\n\n## Context\n\nFollow-up to #6188; related definition and execution metadata work: #6982 and #6983.\n\nStarting points: [Chronon offline adapter](https://github.com/feast-dev/feast/blob/master/sdk/python/feast/infra/offline_stores/contrib/chronon_offline_store/chronon.py), [monitoring storage contract](https://github.com/feast-dev/feast/blob/master/sdk/python/feast/infra/offline_stores/offline_store.py), [MonitoringService](https://github.com/feast-dev/feast/blob/master/sdk/python/feast/monitoring/monitoring_service.py), and [Chronon online adapter](https://github.com/feast-dev/feast/blob/master/sdk/python/feast/infra/online_stores/chronon_online_store/chronon.py).\n","author":{"url":"https://github.com/franciscojavierarceo","@type":"Person","name":"franciscojavierarceo"},"datePublished":"2026-10-09T04:45:00Z","url":"https://github.com/feast-dev/feast/issues/6984"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:49208322-c004-402e-4bfe-4168cfdc6e54 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D8EA:237BB8:2B9E88:3C2340:6AFE9811 |
| html-safe-nonce | 87e94ebcd8d69efce94fe7e0a698bc0227246aa79382b0eb1b1e8e197294855f |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEOEVBOjIzN0JCODoyQjlFODg6M0MyMzQwOjZBRkU5ODExIiwidmlzaXRvcl9pZCI6IjUxNjk3NTQ4MjkyMTEyMTE3OTMiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 21f49d1b8e00e2d523acbc6d05d0026dab6efd44870527b334217680b2c24262 |
| hovercard-subject-tag | issue:5772902787 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/feast-dev/feast/6984/issue_layout |
| twitter:image | https://opengraph.githubassets.com/2f0c11d338d3bd84f536ec040ed3793bdbec88eb3794f1e7a5ff66153453e48a/feast-dev/feast/issues/6984 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/2f0c11d338d3bd84f536ec040ed3793bdbec88eb3794f1e7a5ff66153453e48a/feast-dev/feast/issues/6984 |
| og:image:alt | Problem Teams should be able to inspect Chronon feature quality in their existing Feast project. Our working demonstration currently profiles an exported checkout snapshot using a separate Dask/Fil... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | franciscojavierarceo |
| hostname | github.com |
| expected-hostname | github.com |
| None | b3c0f155eafc27e60db6e254d1ffff0e072e9ab3b4018a5ee518797c19d89f86 |
| turbo-cache-control | no-preview |
| go-import | github.com/feast-dev/feast git https://github.com/feast-dev/feast.git |
| octolytics-dimension-user_id | 57027613 |
| octolytics-dimension-user_login | feast-dev |
| octolytics-dimension-repository_id | 161133770 |
| octolytics-dimension-repository_nwo | feast-dev/feast |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 161133770 |
| octolytics-dimension-repository_network_root_nwo | feast-dev/feast |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 4a10310af51a1bfffbedc4fd81cb582acf0cb0ff |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width