Skip to content

Feast UI support of multiple feature stores #3728

@heavenmarshal

Description

@heavenmarshal

Is your feature request related to a problem? Please describe.

In one of my project, there are multiple feature stores in one application. However, the ui server doesn't seem to support it.

I can show the issue with a simplified example. I have two local feature stores with project names store_1 and store_2. At the root folder of store_1, I run

feast ui --port 8890 --root_path /something

when I use my browser to hit http://localhost:8890/, the server logs:

"GET /something/registry HTTP/1.1" 404 Not Found

It is due to the path of registry doesn't include the root_path.

After I change the path of registry to

@app.get(f"{root_path}/registry")

and run two ui servers for the two feature stores by

# at the root folder of store_1
feast ui --port 8890 --root_path /something

# at the root folder of store_2
feast ui --port 8891 --root_path /something-else

then use the browser to hit localhost:8890, the log of the server of store_1 shows

"GET /something-else/registry HTTP/1.1" 404 Not Found

It is because the configuration of store_2 overwrites projects-list.json at here

Describe the solution you'd like

I would suggest to make the following changes

  1. include the root_path into the path of registry,
  2. use an individual projects-list.json (maybe change it to projects-list-<project_id>.json ) for each ui server.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureNew feature or requestwontfixThis will not be worked on

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions