Description

rpathade

opened on May 22, 2026

Issue body actions

Is your feature request related to a problem? Please describe.
The enable/disable/set-state commands for feature view state management (introduced in PR #6401) currently only exist under the feast feature-views CLI group and only support FeatureView and OnDemandFeatureView. There are no REST/gRPC API endpoints for these operations.

Describe the solution you'd like

• Add enable, disable, set-state CLI commands under on-demand-feature-views and stream-feature-views
• Update FeatureStore.enable_feature_view() / disable_feature_view() / set_feature_view_state() to handle StreamFeatureView
• Add REST and gRPC API endpoints for enable, disable, and set-state operations
• Add unit tests for new CLI commands and API endpoints

Additional context
Parent issue: #6331
Follow-up from PR #6401.

Activity

1. rpathade

   added

   kind/featureNew feature or requestNew feature or request

   on May 22, 2026
2. smqd19 commented on May 22, 2026

   

   smqd19

   on May 22, 2026

   More actions

   Extending enable/disable/set-state to all feature view types makes sense, especially for consistency. In our own setups, we've often had to do similar updates to keep feature management in sync across different view types. For the CLI additions, consider leveraging Feast's existing command framework — it's flexible enough to add subcommands under new groups like on-demand-feature-views and stream-feature-views.

   On the API side, using Feast's current gRPC and REST patterns for feature view operations as templates will help ensure the new endpoints are consistent. If you're using protobufs, adding new request/response messages for these actions should be straightforward. Also, unit tests should mock the FeatureStore methods and API handlers separately, to isolate logic. Combining both CLI and API coverage early can prevent regressions down the line.
3. ntkathole

   added

   good first issueGood for newcomersGood for newcomers

   Community Contribution NeededWe want community to contributeWe want community to contribute

   starter-ticketGood starter ticketsGood starter tickets

   on Jun 5, 2026
4. Rakeshpatil01 commented on Jun 30, 2026

   

   Rakeshpatil01

   on Jun 30, 2026

   More actions

   Hi @ntkathole , I am working on this issue. I have the proto changes, registry endpoints, CLI commands, and unit tests ready locally and will submit a PR shortly.

   Reacted by Nikhil Kathole
5. ntkathole

   assigned

   Rakeshpatil01

   on Jun 30, 2026
6. Rakeshpatil01 commented on Jul 2, 2026

   

   Rakeshpatil01

   on Jul 2, 2026

   More actions

   Hi @ntkathole , I have submitted a PR to address this issue: #6580.

   It includes the gRPC server handlers, REST router endpoints, CLI commands for
   stream/on-demand feature views, client-side FeatureStore checks, and a complete
   set of unit and integration tests.
7. nothingyuancando commented on Sep 14, 2026

   

   nothingyuancando

   on Sep 14, 2026

   More actions

   Hi, I would like to take this on. I will first review the existing state-management implementation and propose a scoped plan for extending the missing Feature View types and the REST/gRPC APIs, including compatibility and test coverage, before opening a PR. Please let me know if this is already being worked on or if there are preferred boundaries for an initial contribution.

Issue actions