Skip to content

Decouple On-Demand Features from their Sources #3639

Closed

Description

@radonnachie

Context: Given a data source that holds the relationships between 2 entities in rows, an on-demand feature that is merely the count of relationships per one of the entities is not neatly possible.

Expected Behavior

A feature-service of only an on-demand feature will infer the required data-sources but not merge the on-demand features with the datasources.

Current Behavior

Requesting features with a feature-service of only an on-demand FeatureView will throw an error:

Steps to reproduce

Given a data-source with 2 entities, define an on-demand FeatureView that provides values for the unique-set of one of the entities.
Then define a feature-service that lists only the on-demand FeatureView and not the source FeatureView.

Specifications

  • Version: 0.31
  • Platform: Linux
  • Subsystem: N/A

Possible Solution

Activity

  1. stale commented on Mar 17, 2024

    @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