Title: Remote materialization · Issue #4526 · feast-dev/feast · GitHub
Open Graph Title: Remote materialization · Issue #4526 · feast-dev/feast
X Title: Remote materialization · Issue #4526 · feast-dev/feast
Description: Is your feature request related to a problem? Please describe. We already have an option to run online/offline store queries remotely through feature server and offline server, respectively. This way rbac rules will be applied on operati...
Open Graph Description: Is your feature request related to a problem? Please describe. We already have an option to run online/offline store queries remotely through feature server and offline server, respectively. This w...
X Description: Is your feature request related to a problem? Please describe. We already have an option to run online/offline store queries remotely through feature server and offline server, respectively. This w...
Opengraph URL: https://github.com/feast-dev/feast/issues/4526
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Remote materialization","articleBody":"**Is your feature request related to a problem? Please describe.**\r\nWe already have an option to run online/offline store queries remotely through feature server and offline server, respectively. This way rbac rules will be applied on operations. One piece that's missing is materialization. There are several ways to do this:\r\n\r\n- Keep materialization local, but rely on remote online/offline engines to apply rbac rules. This is currently impossible because remote online client doesn't implement `online_write_batch` method. Even if we did implement it in the feature server itself, we would essentially be using a lightweight fastapi server to transport batches and batches of potentially huge datasets.\r\n\r\n- Create remote materialization engine that will defer the whole materialization call to a backend server and apply rbac rules there. We can create another server component MaterializationServer that will receive these requests.\r\n\r\n- The same as above but instead of creating a new component, we can reuse OfflineServer to do the request handling. This is slightly awkward from the naming perspective, but probably makes the most sense in term of usage/maintenance.\r\n\r\nI'd probably go with option 3 as a starting point.","author":{"url":"https://github.com/tokoko","@type":"Person","name":"tokoko"},"datePublished":"2024-09-17T06:12:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/4526/feast/issues/4526"}
| 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:077f98c9-351f-b19d-8445-e696272eb3f2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | DE14:362FC4:A99BD0A:ACDD314:6A50A5B1 |
| html-safe-nonce | 71e291ef71a7000ce1210a6aae7c0e9f08c6a43e82fd0cff75a1d91c656020d9 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJERTE0OjM2MkZDNDpBOTlCRDBBOkFDREQzMTQ6NkE1MEE1QjEiLCJ2aXNpdG9yX2lkIjoiNDg5MDE5ODEwMDg0NzY2NjYwOSIsInJlZ2lvbl9lZGdlIjoic2VhIiwicmVnaW9uX3JlbmRlciI6InNlYSJ9 |
| visitor-hmac | e4fe0456d27b12edc918921cbda4c89bec249065e9d62ff2cb06171f94b9cec6 |
| hovercard-subject-tag | issue:2530124664 |
| 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/4526/issue_layout |
| twitter:image | https://opengraph.githubassets.com/b257e82c8f4583652bb7079de4f3999deef7c002c245a2716d6fbd4a08d2da89/feast-dev/feast/issues/4526 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/b257e82c8f4583652bb7079de4f3999deef7c002c245a2716d6fbd4a08d2da89/feast-dev/feast/issues/4526 |
| og:image:alt | Is your feature request related to a problem? Please describe. We already have an option to run online/offline store queries remotely through feature server and offline server, respectively. This w... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | tokoko |
| hostname | github.com |
| expected-hostname | github.com |
| None | d6dc8294eb500fa36bbc57472d61fe87c522f9c3c1d64f70f4926f66a66a7efb |
| 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 | 7ac0ad2f2c7e4b9056617355fd9e33e22b0c8df9 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width