Add support to save aggregation metadata on feature view #6283
ps-cbsantos
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I’m relatively new to ML and Feast and I’m trying to understand how the aggregation metadata (used to apply transformations on raw data) is connected to the registry.
What I’d like to achieve:
I want to have a single transformation job (or the smallest number possible) that receives configuration telling it:
This would allow much better reuse and greatly reduce the effort of creating/maintaining multiple transformation jobs.
Am I approaching this the right way? Or am I looking in the wrong place?
How do you guys usually handle this kind of scenario?
Beta Was this translation helpful? Give feedback.
All reactions