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

Feast UI doesn't work with SQLRegistry #2963

Closed
0fair opened this issue Jul 21, 2022 · 2 comments · Fixed by #3028
Closed

Feast UI doesn't work with SQLRegistry #2963

0fair opened this issue Jul 21, 2022 · 2 comments · Fixed by #3028

Comments

@0fair
Copy link

0fair commented Jul 21, 2022

Expected Behavior

Feast UI works correctly
I can see all Data Sources / Feature Views etc

Current Behavior

Nothing is show
Errors in console:

react_devtools_backend.js:4026 ZodError: [
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "featureServices",
      0,
      "meta",
      "createdTimestamp"
    ],
    "message": "Required"
  }
]
    at yk (index.mjs:449:23)
    at n.value (index.mjs:561:16)
    at n.value (index.mjs:541:29)
    at useLoadRegistry.ts:35:47

Steps to reproduce

build feature_store.yaml with SQLRegistry
deploy features to registry via "feast apply"
start webserver with "feast ui"
go to browser and try feast ui

Specifications

  • Version: 0.22.1
  • Platform: arm64
  • Subsystem: macOS

Possible Solution

insert create_timestamp columns into sql registry schema and write code to add it to registry proto
now there is no columns like "created_timestamp" in sql registry

@adchia adchia self-assigned this Aug 6, 2022
@adchia adchia linked a pull request Aug 6, 2022 that will close this issue
@adchia
Copy link
Collaborator

adchia commented Aug 8, 2022

cc @achals

@achals
Copy link
Member

achals commented Aug 9, 2022

Should be fixed by #3033 too

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

Successfully merging a pull request may close this issue.

3 participants