You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How should we store Headless features? and should we?
We MUST have the values for training purposes.
When preparing the FeatureSet: We can run the function against the "key" feature timestamp.
Alternatively, you can run your Headless feature against a DataSource for the sake of "replaying"
What should we do on prod?
should we record the calculations of the "get"?
Alternatively, we might build a special mechanism on the "client-side" that retrieve the FeatureSet(similar to §1.2). This will close the gate over the "simple solution" we have right now for FeatureSet retrieval(= via a view written in SQL)
What do you propose to do?
TBD.
What have you already tried?
No response
What else should we know?
No response
The text was updated successfully, but these errors were encountered:
Background
How should we store Headless features? and should we?
What do you propose to do?
TBD.
What have you already tried?
No response
What else should we know?
No response
The text was updated successfully, but these errors were encountered: