# [0.57.0](
v0.56.0...v0.57.0) (2025-11-13)
### Bug Fixes
* Improve trino to feast type mapping with (real,varchar,timestamp,decimal) ([
#5691](
#5691)) ([
f855ad2](
f855ad2))
* Materialize API - ODFV views not looked-up (thinks views non existant) - crashes materialize ([
#5716](
#5716)) ([
1b050b3](
1b050b3))
* Support historical feature retrieval with start_date/end_date in RemoteOfflineStore ([
#5703](
#5703)) ([
ad32756](
ad32756))
* Thread safe Clickhouse offline store ([
#5710](
#5710)) ([
5f446ed](
5f446ed))
### Features
* Add annotations to cronjob CRDs ([
#5701](
#5701)) ([
be6e6c2](
be6e6c2))
* Add batch commit mode for MySQL OnlineStore ([
#5699](
#5699)) ([
3cfe4eb](
3cfe4eb))
* Add possibility to materialize only latest values, to increase performance ([
#5713](
#5713)) ([
8d77b72](
8d77b72))
* Support table format: Iceberg, Delta, and Hudi ([
#5650](
#5650)) ([
2915ad1](
2915ad1))
What this PR does / why we need it:
On-demand feature views not checked when materialize is called via a web-endpoint /materialize. Which means, ODFV cannot be materialized via an endpoint - FeatureViewNotFoundException gets raised...
Solution: check get_on_demand_feature_view too!
On a bigger scale, this is caused by apparently 3 different implementations of checking whether a feature view exists - logging, server and feature_store (Python SDK). I wouldn't venture into refactoring yet, since we're quite busy, but at least this bugfix unblocks ODFV materialization (which we need a lot).
Also re-organized a bit - imho we should prioritize checking features, odfvs and then stream.