Skip to content

Reorganise ingestion store classes to match architecture  #109

@tims

Description

@tims

Is your feature request related to a problem? Please describe.
The store classes in ingestion are currently all mixed into a single storage package. This makes it difficult to see that there should be a clear distinction between serving stores, warehouse stores, and errors stores.

Describe the solution you'd like
I'd like to propose the following package structure

  • feast.store.warehouse
  • feast.store.serving
  • feast.store.errors

feast.store, will be used for any common classes and interfaces. Naming conventions should follow a similar style to the "source" package.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions