Skip to content

FeastObject type is missing SavedDataset #4312

Closed

Description

@dmartinol

Expected Behavior

FeastObject should include all types of instances applied to the feature store.

Current Behavior

It misses SavedDataset type.

Specifications

  • Version: 0.39.0

Activity

  1. dmartinol commented on Jun 24, 2024

    @dmartinol
    ContributorAuthor
  2. tokoko commented on Jun 24, 2024

    @tokoko
    Collaborator

    Agreed, I'd add that although class BatchFeatureView exists in the codebase, it's basically unused at this point and not part of registry CRUD operations. Even if it was, once #4235 gets resolved, do you think it's still a good idea not to treat FeatureViews as a single object type?

  3. dmartinol commented on Jun 25, 2024

    @dmartinol
    ContributorAuthor

    Can I take this one and send a PR?

  4. tokoko commented on Jun 25, 2024

    @tokoko
    Collaborator

    sure, go ahead

  5. dmartinol commented on Jun 25, 2024

    @dmartinol
    ContributorAuthor

    Even if it was, once #4235 gets resolved, do you think it's still a good idea not to treat FeatureViews as a single object type?

    I'm not against having a single type but I cannot estimate the impacts on the registry (endpoints and diff logic).
    In the permission model we're using a filter to allow selecting only specific types and exclude sub-classes, which again should be reviewed.

    Pls note that OnDemandFeatureView is a BaseFeatureView only, this would either need its entry in FeastObject or to review its hierarchy.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions