Repository navigation
Feature View TTL not Make Sense #3435
Description
Expected Behavior
Note 1 = ttl=timedelta(days=1), need to get day 1 data or one-day data but its gives total data.
Note 2 = when we are not mentioning any minutes in the time stamp of our original data source if give minutes in feast sdk data source code it should give 0 data but it's giving again total data.
Note 3 = when we are mentioned some minutes in the original data source it's giving every data that matches that minutes we didn't understand how exactly this TTL is working.
Current Behavior
Not giving according to TTL Time Stamp as given in expected behavior notes
Steps to reproduce
Specifications
- Version: 0.28
- Platform: Azure Machine Learning Work Space (MSSQL- data base )
- Subsystem:Linux
Activity
stale commentedon May 20, 2023
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
tobby-lie commentedon Jul 17, 2023
I believe I discovered bug related to Note 1:
The
MULTIPLE_FEATURE_VIEW_POINT_IN_TIME_JOINsql query forSnowflakeOfflineStore(my use-case) seems to be usingTTLfor two things:TTLfor the currentfeature_view, also keep the rows where thetimestamp_fieldis higher the the one provided minus theTTLTTLfor the currentfeature_viewthen filter outevent_timestampsolder thanentity_timestamp - TTLSeems like
TTLis just the amount of time that is inspected for a group of features starting from their timestamp and looking back in time from there. Intuitively, I assumedTTLwas more of an "expiration date" where, after an elapsed amount of time from a timestamp, data would no longer be accessible viafeast, it seems this is not the case currently.stale commentedon Mar 17, 2024
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.