GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Feast UI: URL scheme "postgresql" is not supported when specifying SQL registry in `projects-list.json` · Issue #3974 · feast-dev/feast

Feast UI: URL scheme "postgresql" is not supported when specifying SQL registry in projects-list.json #3974

New issue
Copy link
New issue
Copy link
Closed
Closed
Feast UI: URL scheme "postgresql" is not supported when specifying SQL registry in projects-list.json#3974
Copy link
Assignees
jeremyary
Labels
kind/bugpriority/p2wontfixThis will not be worked onThis will not be worked on

Description

@TomSteenbergen
TomSteenbergen
opened on Feb 28, 2024
Issue body actions

Expected Behavior

The UI created using a custom React app with a SQL registry shows the entities, feature views, etc. per project.

Current Behavior

It is unclear how to specify the registryPath in your projects-list.json file. The structure of this file could definitely benefit from some more documentation.

While the Feast UI does spin up and shows the project names and descriptions from the projects-list.json on the homepage, it does not load and visualize the corresponding Feast objects when clicking on one of these projects, even though the registry does contain that data (see screenshot).

image

The browser console shows the following error:

Fetch API cannot load postgresql://postgres:test@db:5432/feast. URL scheme "postgresql" is not supported.

The part postgresql://postgres:test@db:5432/feast is the connection string to my SQL registry that I created through docker-compose and that I pass in projects-list.json under the registryPath key.

Is a SQL registry is not supported yet by the UI? Or did I format registryPath incorrectly?

Steps to reproduce

  1. Follow steps from the docs to create a React app.
  2. Add your projects-list.json to the public directory. My file looked like this:
{
  "projects": [
    {
      "name": "Project 1",
      "description": "Description 1.",
      "id": "project_1",
      "registryPath": "postgresql://postgres:test@db:5432/feast"
    },
    {
      "name": "Project 2",
      "description": "Description 2.",
      "id": "project_2",
      "registryPath": "postgresql://postgres:test@db:5432/feast"
    }
  ]
}
  1. Start a Postgres database using the following docker-compose.yml
version: "3"
services:
  db:
    restart: always
    image: postgres:16-alpine
    ports:
      - "5432:5432"
    networks:
      - backend
    volumes:
      - ~/feast_postgres_data:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB=feast
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=test
networks:
  backend:
    driver: bridge

volumes:
  feast_postgres_data: null
  1. Run yarn start.

Specifications

  • Version: 0.35.0
  • Platform: MacOS
  • Subsystem: Sonoma 14.2

Possible Solution

More documentation on setting up the UI would be very much welcome.

Activity

  1. TomSteenbergen
    added
    kind/bug
    priority/p2
    on Feb 28, 2024
  2. TomSteenbergen
    changed the title [-]Feast UI: Unclear how to host for multiple projects using single SQL registry[/-] [+]Feast UI: URL scheme "postgresql" is not supported when specifying SQL registry in `projects-list.json`[/+] on Feb 28, 2024
  3. jeremyary commented on Mar 4, 2024

    @jeremyary
    jeremyary
    on Mar 4, 2024
    Collaborator
    More actions

    Hey @TomSteenbergen thanks for raising your issue. My initial suspicion is that the postgres protocol isn't supported for UI's registryPath, so we're looking into this to confirm. Should this be the case, we'll take a look at a docs update to better specify possible values there &, if appropriate based on findings, potentially open another issue to consider supporting the protocol as a feature request. We'll keep you posted here.

    Reacted by Tom Steenbergen
  4. jeremyary
    self-assigned this
    on Mar 4, 2024
  5. tmihalac
    added a commit that references this issue on Mar 5, 2024

    fix: Added registryPath parameter documentation

    5564994
  6. tmihalac commented on Mar 5, 2024

    @tmihalac
    tmihalac
    on Mar 5, 2024
    Contributor
    More actions

    Currently registryPath parameters supports only a file location or url value.

    Will add a note in the reference documentation mentioning that.

  7. tmihalac
    added a commit that references this issue on Mar 5, 2024

    fix: Added registryPath parameter documentation

    a76d915
  8. haoxu0
    added a commit that references this issue on Mar 5, 2024

    fix: Added registryPath parameter documentation in WebUI reference (#…

    5e0af8f
  9. TomSteenbergen commented on Mar 7, 2024

    @TomSteenbergen
    TomSteenbergen
    on Mar 7, 2024
    ContributorAuthor
    More actions

    Currently registryPath parameters supports only a file location or url value.

    @tmihalac Thanks for confirming! Do you happen to know whether support for a SQL registry is somewhere on the roadmap?

  10. jeremyary commented on Mar 7, 2024

    @jeremyary
    jeremyary
    on Mar 7, 2024
    Collaborator
    More actions

    @TomSteenbergen I feel we're still working on our community roadmap & I can't unilaterally say with certainty, but I can share that there's been interest outside of your own expressed in seeing SQL-based registry/offline/online followed up so I'd think it's likely to be explored.

    Reacted by Tom Steenbergen and zerafachris
  11. lokeshrangineni
    added a commit that references this issue on Mar 7, 2024

    fix: Added registryPath parameter documentation in WebUI reference (f…

    5287a57
  12. haoxu0
    added 2 commits that reference this issue on Mar 9, 2024

    fix: Added registryPath parameter documentation in WebUI reference (#…

    1dc81ec

    merge master (#4002)

    29d1e94
  13. tqtensor
    added a commit that references this issue on Mar 11, 2024

    fix: Added registryPath parameter documentation in WebUI reference (f…

    81dce45
  14. tokoko commented on Mar 19, 2024

    @tokoko
    tokoko
    on Mar 19, 2024
    Collaborator
    More actions

    We recently added grpc registry server in #3924. The intention for it was to be used from go and java servers, but i guess it could be a solution in here as well... if someone figures out a way to call grpc from the browser :) and get the registry proto from there.

    Reacted by Shuchu Han
  15. franciscojavierarceo
    added a commit that references this issue on Apr 16, 2024

    chore(release): release 0.36.0

    474eb62
  16. stale commented on Apr 26, 2025

    @stale
    staleBot
    on Apr 26, 2025 – with Stale
    More actions

    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.

  17. stale
    added
    wontfixThis will not be worked onThis will not be worked on
    on Apr 26, 2025
  18. stale
    closed this as completedon May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @jeremyary
    jeremyary

Labels

kind/bugpriority/p2wontfixThis will not be worked onThis 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

    You are visitor 01402520 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.