Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decouple On-Demand Features from their Sources #3639

Open
radonnachie opened this issue May 26, 2023 · 1 comment
Open

Decouple On-Demand Features from their Sources #3639

radonnachie opened this issue May 26, 2023 · 1 comment
Labels
kind/bug priority/p2 wontfix This will not be worked on

Comments

@radonnachie
Copy link
Contributor

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

Copy link

stale bot commented Mar 17, 2024

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
Labels
kind/bug priority/p2 wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant