Feast Roadmap Prioritization
The form below is used to drive the prioritization of the Feast roadmap. Please let us know what the top priority of Feast contributors should be.
If you want a new item added to this list, please create an issue over here
Sign in to Google
to save your progress.
What functionality should we prioritize for Feast?
Adding support for running Feast as a service (HTTP or gRPC API)
Adding a Feast UI
Adding support for my new data sources or offline stores
Adding support for feature engineering on streaming data
Optimizing the performance of Feast (ingesting data, building training datasets, or read-time latency and throughput)
Adding the ability to write/push feature data to Feast
Adding support for feature engineering on batch data
Adding support for new online store(s)
Improving the Feast documentation or tutorials
Adding support for streaming ingestion
Adding support for creating and managing offline historical copies of production data
Making Feast easier to extend (pluggable offline stores, online stores, compute engines
Adding support for on-demand transformations
Adding support for feature versioning
Adding support for data quality monitoring/validation integration (with great expectations)
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google.
Terms of Service