Is your feature request related to a problem? Please describe.
Feast should manage a well defined a state machine from creation of a feature view, generation of feature using engineering, and then materialisation. Something like created, generated, available_online and so on . And possibly one status mechanism also. Something like enabled/disabled. So for example, you'll be able to read some online feature iff feature view is BOTH available_online and enabled.
Describe the solution you'd like
An end to end state machine for above use case
Describe alternatives you've considered
New request. Really nothing in place for it.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
Feast should manage a well defined a state machine from creation of a feature view, generation of feature using engineering, and then materialisation. Something like created, generated, available_online and so on . And possibly one status mechanism also. Something like enabled/disabled. So for example, you'll be able to read some online feature iff feature view is BOTH available_online and enabled.
Describe the solution you'd like
An end to end state machine for above use case
Describe alternatives you've considered
New request. Really nothing in place for it.
Additional context
Add any other context or screenshots about the feature request here.