Skip to content

apply_materialization for Remote Registry fails for Stream Feature Views #4271

Closed

Description

@msistla96

Expected Behavior

apply_materialization for Remote Registry should work for Stream Feature Views. Discovered as part of #4257 when running integration tests.

Current Behavior

apply_materialization for Remote Registry throws the below error when trying to materialize a stream feature view:
TypeError: Parameter to MergeFrom() must be instance of same class: expected <class 'feast.core.FeatureView_pb2.FeatureView'> got <class 'feast.core.StreamFeatureView_pb2.StreamFeatureView'>.

Steps to reproduce

  1. Setup Remote Registry
  2. Call apply_materialization and pass a stream feature view as the feature view.

Specifications

  • Version: Python 3.9
  • Platform: Mac OSX
  • Subsystem: Sonoma 14.4.1

Possible Solution

ApplyMaterializationRequest of the RegistryServer proto should be updated to allow the StreamFeatureView proto to be passed when making the request from Remote Registry via RegistryServer.

Activity

  1. stale commented on Apr 26, 2025

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions