◐ Shell
clean mode source ↗

fix: Add project_id filter to SnowflakeRegistry UPDATE path by Abhishek8108 · Pull Request #6243 · feast-dev/feast

Abhishek8108

devin-ai-integration[bot]

@ntkathole ntkathole changed the title fix: add project_id filter to SnowflakeRegistry UPDATE path fix: Add project_id filter to SnowflakeRegistry UPDATE path

Apr 10, 2026

ntkathole

ntkathole

_apply_object had a missing project_id clause in the UPDATE branch's
WHERE condition. In a shared Snowflake registry, this allowed a
feast apply in one project to silently overwrite a same-named object
belonging to a different project.

The SELECT path already scoped correctly by project_id. The DELETE
path (_delete_object) also scoped correctly. This commit brings the
UPDATE path in line with both.

Fixes feast-dev#6208

Signed-off-by: Abhishek8108 <87538407+Abhishek8108@users.noreply.github.com>
…stry UPDATE

- Reformat with-statement blocks to parenthesized form (ruff format)
- Add test_apply_object_does_not_overwrite_sibling_project: simulates two
  projects sharing a registry, applies an object to project_b, and asserts
  the UPDATE WHERE clause is scoped to project_b and does not reference
  project_a — direct regression coverage for feast-dev#6208

Signed-off-by: Abhishek8108 <87538407+Abhishek8108@users.noreply.github.com>
Signed-off-by: Abhishek8108 <87538407+Abhishek8108@users.noreply.github.com>