GeezerVison is showing github.com — Doc: Document feature store objects deletion from feast · Issue #5360 · feast-dev/feast
Doc: Document feature store objects deletion from feast #5360DescriptionIs your feature request related to a problem? Please describe.
Feast currently supports the objects deletion from registry, but its not documented yet. The object deletion is done via : feast.apply(objects_to_delete=[feature_view1])
Describe the solution you'd like
- Document the object deletion using a jupyter notebook that:
- Creates feature store objects.
- Read the feature store objects.
- Deletes the objects.
- Validate the deleted objects are not available.
- [Optional] Write an unit test.
Activityfranciscojavierarceo commented on May 16, 2025 I also recently added a CLI too l for this too. #5344 obielin commented on May 4, 2026 Hi, I'd like to take this one. Plan: add a new examples/object-deletion/ directory with a notebook that creates a small feature store, registers a couple of feature views and entities with feast apply, lists them, deletes one using feast.apply(objects_to_delete=[...], partial=False), then confirms it's gone. I'll also add a one-line entry in examples/README.md linking to it. Will open a PR shortly. Henildiyora commented on Jun 7, 2026 Hi @obielin — looks like you planned to open a PR for this back in May. Are you still actively working on it?
If not, I'd love to pick this up. Happy to coordinate if you've already made progress locally. @jyejare @franciscojavierarceo — any guidance on whether this is still up for grabs? jyejare commented on Jun 8, 2026 CollaboratorAuthor More actions @Henildiyora There is a bit of hint about object deletion in docs/getting-started/components/registry.md which I think is sufficient. Do you have different / more thoughts on that ? Henildiyora commented on Jun 9, 2026 @jyejare Thanks for pointing me to the file!
I went through the current docs/getting-started/components/registry.md carefully. Honestly, the deletion section is already quite solid — the warning about feast apply not deleting objects, the CLI command, the Python SDK methods, and the partial=False hint are all there.
That said, I noticed one small gap: there is no end-to-end code snippet showing the full lifecycle in one place — create → list/verify → delete → confirm deletion. Right now a new user has to mentally connect multiple pieces across the file to understand the complete flow.
A small addition I could make directly to registry.md would be a single runnable code block like this:
from feast import FeatureStore
store = FeatureStore(repo_path=".")
# 1. Verify object exists before deletion
print(store.list_feature_views()) # shows driver_stats
# 2. Delete using the explicit method
store.delete_feature_view("driver_stats")
# 3. Confirm it's gone
print(store.list_feature_views()) # now emptyThis would make the section self-contained and immediately copy-pasteable for users. Would that addition be welcome as a small PR? Or do you feel the current state is already sufficient to close the issue? obielin commented on Jun 10, 2026 Apologies for the long silence on this @jyejare @Henildiyora life got in the way of my original plan.
Having re-read docs/getting-started/components/registry.md, I agree the existing deletion docs are already solid (the feast apply warning, CLI command, SDK methods, and partial=False note are all there). A full new notebook / examples directory feels like overkill for what's actually missing.
The one real gap is that there's no single, self-contained lifecycle example in one place. I'm still happy to take this — I'll keep it minimal and just add a short runnable snippet to registry.md showing create → verify → delete → confirm, so the section is copy-pasteable end-to-end. Will open a small PR for that.
@Henildiyora thanks for the thorough review and the suggested snippet — happy to coordinate if you'd rather drive it. obielin commented on Jun 10, 2026 Apologies for the long silence on this @jyejare @Henildiyora life got in the way of my original plan.
Having re-read docs/getting-started/components/registry.md, I agree the existing deletion docs are already solid (the feast apply warning, CLI command, SDK methods, and partial=False note are all there). A full new notebook / examples directory feels like overkill for what's actually missing.
The one real gap is that there's no single, self-contained lifecycle example in one place. I'm still happy to take this — I'll keep it minimal and just add a short runnable snippet to registry.md showing create → verify → delete → confirm, so the section is copy-pasteable end-to-end. Will open a small PR for that.
@Henildiyora thanks for the thorough review and the suggested snippet — happy to coordinate if you'd rather drive it. Henildiyora commented on Jun 10, 2026 @obielin No worries at all — happy to hand this back to you! You were here first and your plan sounds exactly right.
Feel free to drive the PR. If it helps, the snippet I drafted earlier is yours to use or adapt however you like. Looking forward to seeing it land!
@jyejare thanks for the patience on this one. Reacted by Linda Oraegbunam jyejare commented on Jun 10, 2026 CollaboratorAuthor More actions Thanks both @obielin and @Henildiyora for your critical communication to solve the issue. I am happy that we all reached to similar solution. Because of you people, Community Shines :)
@obielin please proceed to raise a PR and I am happy to request @Henildiyora for review. Reacted by Linda Oraegbunam obielin commented on Jun 11, 2026 I've opened #6504 for this. It adds a self-contained end-to-end deletion lifecycle example (list/verify → delete → confirm) to docs/getting-started/components/registry.md, plus a test_apply_delete_feature_view unit test covering deletion via apply(objects_to_delete=[...], partial=False).
@jyejare happy to have @Henildiyora review whenever convenient. Thanks again both for the helpful discussion! johndelara1 commented on Jun 23, 2026 Update: I just saw the follow-up discussion and PR #6504. Since the maintainers and contributors converged on a smaller documentation-focused change in docs/getting-started/components/registry.md, I won’t open a competing notebook PR.
Happy to help by reviewing or testing #6504 if useful. Thanks for coordinating this!
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|