-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Get only latest data from online store features #5160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
You're correct — the online store in Feast is meant to serve the latest data for a given entity. When you materialize data (e.g., from your offline store containing Jan–Mar 2025 data), only the most recent row per entity (based on event timestamp) will be pushed to the online store. The online store retains just the latest value for each entity-feature combination by default — older data gets overwritten, not retained. For example, if an entity has values for January and February, and you later materialize March data, the March value will overwrite the earlier values in the online store. |
Thank you for the explanation!
…________________________________
From: Hao Xu ***@***.***>
Sent: Friday, March 28, 2025 6:33 AM
To: feast-dev/feast ***@***.***>
Cc: Vidhya Pandi ***@***.***>; Author ***@***.***>
Subject: Re: [feast-dev/feast] Get only latest data from online store features (Issue #5160)
You're correct — the online store in Feast is meant to serve the latest data for a given entity. When you materialize data (e.g., from your offline store containing Jan–Mar 2025 data), only the most recent row per entity (based on event timestamp) will be pushed to the online store. The online store retains just the latest value for each entity-feature combination by default — older data gets overwritten, not retained.
For example, if an entity has values for January and February, and you later materialize March data, the March value will overwrite the earlier values in the online store.
—
Reply to this email directly, view it on GitHub<#5160 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIBPKIAVYWEGV4P2GKRAO5D2WSNWLAVCNFSM6AAAAABZGDSABWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJZHEYTKOBXGE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
[HaoXuAI]HaoXuAI left a comment (feast-dev/feast#5160)<#5160 (comment)>
You're correct — the online store in Feast is meant to serve the latest data for a given entity. When you materialize data (e.g., from your offline store containing Jan–Mar 2025 data), only the most recent row per entity (based on event timestamp) will be pushed to the online store. The online store retains just the latest value for each entity-feature combination by default — older data gets overwritten, not retained.
For example, if an entity has values for January and February, and you later materialize March data, the March value will overwrite the earlier values in the online store.
—
Reply to this email directly, view it on GitHub<#5160 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIBPKIAVYWEGV4P2GKRAO5D2WSNWLAVCNFSM6AAAAABZGDSABWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJZHEYTKOBXGE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
|
Expected Behavior
I think serving features via online store makes sense if we serve the recent or latest data for any given entity. Suppose I have my patient data from Jan-Mar 2025 in offline store. Then I run materialization command to push the latest changes eg. March data to the online store.
My question is whether the old data in the online store will retain, or it will be overridden by the new data of March month.
Current Behavior
I know we can get online features based on the entities. Wondering am I missing something which already exists in other terms like ttl or any other ways we can achieve so that to get the online features in an incremental way instead of depending on materialization.
Steps to reproduce
Specifications
Possible Solution
The text was updated successfully, but these errors were encountered: