You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add feature view versioning support to Remote online store #6180
Add versioned feature view read/write support to the Remote online store, so that version-qualified feature references (e.g., driver_stats@v2:trips_today) resolve to the correct versioned data.
Context
Feature view versioning was introduced in #6101. Currently, only the SQLite online store supports versioned reads/writes. All other online stores raise VersionedOnlineReadNotSupported when a versioned ref is used.
The implementation pattern (see sqlite.py for reference) involves:
Write path: When enable_online_feature_view_versioning is enabled, materialize data into a version-specific table/key namespace (e.g., {project}_{fv_name}_v{version})
Read path: Route version-qualified lookups to the correct versioned table/key namespace
I’ve gone through the context and the reference implementation in sqlite.py, and I understand that the goal is to extend versioned feature view support to the Remote online store by implementing version-aware read/write paths.
My approach would be:
Implement version-specific namespaces for writes (e.g., {project}_{feature_view}_v{version}) when enable_online_feature_view_versioning is enabled
Route version-qualified reads to the correct versioned keys/tables
Align the behavior closely with the existing SQLite implementation for consistency
Add tests to validate correct behavior across multiple feature view versions
I’ve already started exploring remote.py and related modules, and I’m confident I can take this forward. Please let me know if this approach aligns with your expectations or if there are any design considerations I should follow.
Activity
shuvakant6623 commentedon Mar 27, 2026
Hi @franciscojavierarceo, I’d like to work on this issue (#6180).
I’ve gone through the context and the reference implementation in
sqlite.py, and I understand that the goal is to extend versioned feature view support to the Remote online store by implementing version-aware read/write paths.My approach would be:
{project}_{feature_view}_v{version}) whenenable_online_feature_view_versioningis enabledI’ve already started exploring
remote.pyand related modules, and I’m confident I can take this forward. Please let me know if this approach aligns with your expectations or if there are any design considerations I should follow.Thanks!