Title: Improved feature view and model versioning · Issue #2728 · feast-dev/feast · GitHub
Open Graph Title: Improved feature view and model versioning · Issue #2728 · feast-dev/feast
X Title: Improved feature view and model versioning · Issue #2728 · feast-dev/feast
Description: Problem When using Feast, it can be hard to version features with respect to models in production. Users modifying a re-used feature view (e.g. in response to upstream schema change) can accidentally impact other models in production Har...
Open Graph Description: Problem When using Feast, it can be hard to version features with respect to models in production. Users modifying a re-used feature view (e.g. in response to upstream schema change) can accidental...
X Description: Problem When using Feast, it can be hard to version features with respect to models in production. Users modifying a re-used feature view (e.g. in response to upstream schema change) can accidental...
Opengraph URL: https://github.com/feast-dev/feast/issues/2728
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Improved feature view and model versioning","articleBody":"# Problem\r\nWhen using Feast, it can be hard to version features with respect to models in production. \r\n- Users modifying a re-used feature view (e.g. in response to upstream schema change) can accidentally impact other models in production\r\n- Hard to tie versions of features together or versions of models (~`FeatureService`)\r\n\r\nAs Feast adds batch transformations or #2597, transformation logic will also need to be versioned. This is already an issue today with on demand feature views too. \r\n\r\n# Potential solution\r\nOne way to address this is to double down on:\r\n### 1. Feature services as the central way to retrieve features + track models. \r\n - Registering a feature service signifies dependent features / feature views are in \"production\"\r\n - Allow `feature_service.get_historical_features` or `feature_service.get_online_features`\r\n### 2. Improvements to `feast plan` and `feast apply`\r\n - `feast plan` that prevents deletion or editing of feature views that feature services in prod depend on (Modifying https://github.com/feast-dev/feast/blob/master/sdk/python/feast/feature_store.py#L594)\r\n - If you remove a feature service, then the underlying feature views could be removed if no other feature service depend on it\r\n - `feast apply` that fails in above case by default (overridable though)\r\n - e.g. modifying the logic at https://github.com/feast-dev/feast/blob/master/sdk/python/feast/feature_store.py#L676\r\n### 3. Feature view versioning\r\n - Not super sure here on the best practice, but a way to say that feature view B is a new version of feature view A.\r\n\r\n","author":{"url":"https://github.com/adchia","@type":"Person","name":"adchia"},"datePublished":"2022-05-23T18:49:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/2728/feast/issues/2728"}
| 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:98d177b9-8407-299d-7aa7-ef8a98d387de |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 96FE:4D341:9DD262:D51F65:6A4D7161 |
| html-safe-nonce | 337723ba4f0ef2870128fa6de53a6c6bd0a1727c846bf6ca48a3d92a24ee2d66 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5NkZFOjREMzQxOjlERDI2MjpENTFGNjU6NkE0RDcxNjEiLCJ2aXNpdG9yX2lkIjoiNjk1NjcxOTM5MzY5MTAzNzEzIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 10fef9c4455e78b3a13c6d9a098314352238a60e43558c23d516e22dea8cf89f |
| hovercard-subject-tag | issue:1245569638 |
| 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/2728/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d5b896f61f46ef054d12e1c522cb65ad04c1775b9a0d2a9b4babdbc15e00370f/feast-dev/feast/issues/2728 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d5b896f61f46ef054d12e1c522cb65ad04c1775b9a0d2a9b4babdbc15e00370f/feast-dev/feast/issues/2728 |
| og:image:alt | Problem When using Feast, it can be hard to version features with respect to models in production. Users modifying a re-used feature view (e.g. in response to upstream schema change) can accidental... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | adchia |
| hostname | github.com |
| expected-hostname | github.com |
| None | c78260c7b3f4ac4b0356c8208537f05406a3a2d46a9ec3f735b372dcc519c39e |
| 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 | 399fff412f48461d435721c009efc17ea44be72f |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width