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

Tables disappear after task run when adding one or more tables to DenyList #1474

Open
matt-kodex opened this issue Jul 8, 2024 · 0 comments

Comments

@matt-kodex
Copy link

matt-kodex commented Jul 8, 2024

Version of the project you're using.

Using commit #1453

Code (or even better whole projects) which reproduce the issue.

n/a

Steps which reproduce the issue.

  1. Using a query engine and metastore on a postgres database having default (public) schema.
  2. Run the metastore task. All tables appear in left nav panel under Tables 'public' section.
  3. Add to the metastore DenyList one or more tables to block access to. These are added with the schema (eg "public.table_1", "public.table_2").
  4. Click Save on the metastore.
  5. These tables are now correctly blocked when trying to query against them.
  6. Public schema still shows all tables.
  7. "Run" the task in the metastore.
  8. The Public schema in the tables tab is now entirely gone.

Note: Removing all items from DenyList and re-running the metastore task brings back the public schema and tables.

Screenshots, GIFs or videos (if relavent).

n/a

Stack traces for crashes.

n/a

Any logs produced.

n/a

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

No branches or pull requests

1 participant