Title: reproducible historical feature queries · Issue #2980 · feast-dev/feast · GitHub
Open Graph Title: reproducible historical feature queries · Issue #2980 · feast-dev/feast
X Title: reproducible historical feature queries · Issue #2980 · feast-dev/feast
Description: Is your feature request related to a problem? Please describe. I'd like a way to use Feast to run the exact same historical query and reproduce the same result the next day regardless of "late arriving" or "restating" data. For example: ...
Open Graph Description: Is your feature request related to a problem? Please describe. I'd like a way to use Feast to run the exact same historical query and reproduce the same result the next day regardless of "late arri...
X Description: Is your feature request related to a problem? Please describe. I'd like a way to use Feast to run the exact same historical query and reproduce the same result the next day regardless of "...
Opengraph URL: https://github.com/feast-dev/feast/issues/2980
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"reproducible historical feature queries","articleBody":"**Is your feature request related to a problem? Please describe.**\r\n\r\nI'd like a way to use Feast to run the exact same historical query and reproduce the same result the next day regardless of \"late arriving\" or \"restating\" data.\r\n\r\nFor example: If I called `get_historical_features` Tuesday at noon to run a model: On Wednesday I'd like to be able to run the run a new and improved model over the same data (to prove it really is a better model, not just benefiting from newer or better data). I don't see a way to pass `created_timestamp=Tuesday@noon` to `get_historical_features` to do that. \r\n\r\n**Describe the solution you'd like**\r\nI presume that a parameter like `max_created_time` would be passed to `get_historical_features`.\r\n\r\n**Describe alternatives you've considered**\r\n Some offline stores have a built in snapshot or time travel capabilities. These generally have limited retention windows and would still require changes to the queries used by feast to take advantage of.\r\n\r\n**Additional context**\r\nFor context I'm working on scenarios where we are not the primary observer of the events in our database. We might learn from a 3rd party at time X that an event happened at time Y, or learn at time A that a prediction was made at time B for what would happen at future time C. We spend a lot of effort reasoning about which timestamps actually gives a sane ordering, and those different timestamps are sometimes relatively far apart.\r\n","author":{"url":"https://github.com/cburroughs","@type":"Person","name":"cburroughs"},"datePublished":"2022-07-28T18:41:46Z","url":"https://github.com/feast-dev/feast/issues/2980"}
| 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:18bc9ebf-1c9a-0615-15bb-3b53f57ff18a |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D21E:22BB81:FCAF8E:14CE0B0:6AFE999E |
| html-safe-nonce | 85e876958c02f2e2c5363d4214c25c323a2664a9ac2f3a86a6a3b7d4850e717d |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEMjFFOjIyQkI4MTpGQ0FGOEU6MTRDRTBCMDo2QUZFOTk5RSIsInZpc2l0b3JfaWQiOiIzNzQwMzYzNzk3MjY5NzQ4MTI3IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 8193ee0496e66282f25938020efbda27a6811d77986d10f961740c1bd37a2f7b |
| hovercard-subject-tag | issue:1321341708 |
| 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/2980/issue_layout |
| twitter:image | https://opengraph.githubassets.com/e1f75cac8565c9761021b6be65dfdedaf329cb3aefd1b9b7cca61440b0958f5c/feast-dev/feast/issues/2980 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/e1f75cac8565c9761021b6be65dfdedaf329cb3aefd1b9b7cca61440b0958f5c/feast-dev/feast/issues/2980 |
| og:image:alt | Is your feature request related to a problem? Please describe. I'd like a way to use Feast to run the exact same historical query and reproduce the same result the next day regardless of "late arri... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | cburroughs |
| 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