There was a problem hiding this comment.
looking good... just a couple nits so far
Sorry, something went wrong.
There was a problem hiding this comment.
otherwise, lgtm
Sorry, something went wrong.
| var ValidOfflineStoreFilePersistenceTypes = []string{ | ||
| "dask", | ||
| "duckdb", | ||
| "file", |
There was a problem hiding this comment.
it appears this is the same as dask... so maybe we don't include it.
Sorry, something went wrong.
There was a problem hiding this comment.
thoughts?
Sorry, something went wrong.
There was a problem hiding this comment.
It is supported and not deprecated yet, so I think we should include it as well
Sorry, something went wrong.
There was a problem hiding this comment.
it was removed from the doc since v0.40
https://docs.feast.dev/v0.40-branch/reference/offline-stores/overview
Sorry, something went wrong.
There was a problem hiding this comment.
it was removed from the doc since v0.40 https://docs.feast.dev/v0.40-branch/reference/offline-stores/overview
But not the code and is not deprecated in the code
Sorry, something went wrong.
| "spark", | ||
| "postgres", | ||
| "feast_trino.trino.TrinoOfflineStore", | ||
| "trino", |
There was a problem hiding this comment.
the docs are using "feast_trino.trino.TrinoOfflineStore" in the example configs. Is there an issue tracking the defect? otherwise, you can simply fix it here 😉
Sorry, something went wrong.
There was a problem hiding this comment.
@dmartinol it appears the docs are out of date ... here's the code where these classes/types are declared -
feast/sdk/python/feast/repo_config.py
Lines 87 to 100 in a36f7e5
Sorry, something went wrong.
There was a problem hiding this comment.
This is what I was trying to suggest: raise an issue (optional) and fix the docs.
Sorry, something went wrong.
There was a problem hiding this comment.
ah ... agree @dmartinol
Sorry, something went wrong.
There was a problem hiding this comment.
Opened an issue #4837
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm apart from minor comments
Sorry, something went wrong.
What this PR does / why we need it:
The fix is to throw an error only if these fields are set and do not match the CR configured persistence type for that service.
The fix is to add CR validation for missing types