René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Not able to set cache configs for file-based registry in Feast Operator","articleBody":"## Expected Behavior \n\nUsers should be able to configure `cache_ttl_seconds` and `cache_mode` for file-based registries, similar to how it works for DB-based registries. \n\n## Current Behavior\n\nThe Feast Operator CRD does not support configuring `cache_ttl_seconds` and `cache_mode` registry settings when using file-based registry persistence. These settings are important for controlling registry caching behavior and are supported by the Feast Python SDK, but cannot be set via the operator CRD for file-based registries.\n\nThis works fine for when using a database-backed registry (SQL or Snowflake), you can configure `cache_ttl_seconds` and `cache_mode` via secrets. This works because DB-based registry configurations pass through all secret parameters via `DBParameters` in the operator's `RegistryConfig` struct.\n\nThere's no mechanism to pass additional registry configuration parameters.\n\n## Possible Solution\n\n\n**Option 1: Add fields to `RegistryFilePersistence`**\n```yaml\nspec:\n  services:\n    registry:\n      local:\n        persistence:\n          file:\n            path: s3://bucket/registry.db\n            cache_ttl_seconds: 60\n            cache_mode: sync\n```\n\n**Option 2: Add a generic config field**\n```yaml\nspec:\n  services:\n    registry:\n      local:\n        persistence:\n          file:\n            path: s3://bucket/registry.db\n            config:\n              cache_ttl_seconds: 60\n              cache_mode: sync\n```\n","author":{"url":"https://github.com/ntkathole","@type":"Person","name":"ntkathole"},"datePublished":"2025-11-03T07:15:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/5708/feast/issues/5708"}