Repository navigation
Closed
Labels
Description
Expected Behavior
When a new object is inserted into the registry, the UI should show it.
Current Behavior
When applying new objects to the Feature Registry the cache is not refreshed, so in the UI they new objects are not shown
Steps to reproduce
Config:
project: feast_experiment
registry:
registry_type: sql
path: postgresql+psycopg://registry_user:registry_pass@feast_registry_db:5432/feast_registry
sqlalchemy_config_kwargs:
echo: false
pool_pre_ping: true
provider: local
online_store:
type: redis
connection_string: feast_online_store:6379
offline_store:
type: postgres
host: feast_offline_db
port: 5432
user: offline_user
password: offline_pass
database: feast_offline
entity_key_serialization_version: 3
auth:
type: no_auth
Docker Compose:
services:
feature_server:
container_name: feast_ui
image: quay.io/feastdev/feature-server:latest
command: feast --log-level=DEBUG -c /feature_repo ui -h 0.0.0.0
volumes:
- ./configs/docker_compose:/feature_repo
ports:
- 8888:8888
feast_offline_db:
image: postgres:15.6
container_name: feast_offline_db
restart: unless-stopped
environment:
POSTGRES_USER: offline_user
POSTGRES_PASSWORD: offline_pass
POSTGRES_DB: feast_offline
ports:
- "5428:5432"
volumes:
- ./backend/offline_db:/var/lib/postgresql/data
feast_registry_db:
image: postgres:15.6
container_name: feast_registry_db
restart: unless-stopped
environment:
POSTGRES_USER: registry_user
POSTGRES_PASSWORD: registry_pass
POSTGRES_DB: feast_registry
ports:
- "5439:5432"
volumes:
- ./backend/regitry_db:/var/lib/postgresql/data
feast_online_store:
image: redis:7.2
container_name: feast_online_store
restart: unless-stopped
ports:
- "6375:6379"
volumes:
- ./backend/online_db:/data
Specifications
- Version: feast==0.53.0
- Platform: amd64
- Subsystem: linux
Possible Solution
Not sure what is happening in the refresh logic.
Reacted by Matías Chaud
Activity
scottmelhop commentedon Sep 9, 2025
FYI, if I serve the registry, and connect to it from the ui using remote, then the failure to refresh the cache happens both on the UI, and on the registry servers.
matiaschaud commentedon Sep 12, 2025
I'm experiencing the same issue, I have to rollout my feast-ui deployment to update the ui with lastest registry.db status.
In my case I'm using s3 minio as registry, not postgres
franciscojavierarceo commentedon Sep 29, 2025
fixed by #5604