René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add plan mode support to SQL registry for feature view versioning","articleBody":"## Summary\n\nThe proto-based (file) registry supports `feast plan` which shows a dry-run diff of what would change before `feast apply`. The SQL registry does not yet have equivalent plan mode support for the feature view versioning flow.\n\nThis includes:\n- Showing version changes (pin/revert) in plan output for the SQL registry\n- Surfacing `FeatureViewPinConflict` errors during `feast plan` (not just `feast apply`)\n- Ensuring the SQL registry's diff logic accounts for version metadata\n\n## Context\n\nFeature view versioning (PR #6101) added version tracking with pin/revert support. The pin conflict detection was added to both the file registry and SQL registry's `apply_feature_view`, but the plan mode path (which previews changes without applying) only works with the file registry today.\n\n## Acceptance criteria\n\n- [ ] `feast plan` correctly previews version pin/revert operations when using the SQL registry\n- [ ] `FeatureViewPinConflict` is raised during plan (not just apply) for the SQL registry\n- [ ] Plan output shows version metadata changes (e.g., \"driver_stats: v1 → v0 (pin)\")\n- [ ] Tests cover plan mode with SQL registry for versioning scenarios","author":{"url":"https://github.com/franciscojavierarceo","@type":"Person","name":"franciscojavierarceo"},"datePublished":"2026-03-13T17:24:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/6104/feast/issues/6104"}