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.

Sign up for GitHub

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

Jump to bottom

"Reset" not work after manual drop tables "public" #1348

Closed
pomazanbohdan opened this issue Jan 9, 2019 · 4 comments
Closed

"Reset" not work after manual drop tables "public" #1348

pomazanbohdan opened this issue Jan 9, 2019 · 4 comments

Comments

@pomazanbohdan
Copy link

pomazanbohdan commented Jan 9, 2019 •
edited
Loading

To solve problems with such a case
#1346

and for the "quick" reinitialization of changes in the database, I suggest adding a 1 button "Untreсk all relationships and tables in the scheme"

Alternatively, another button: "Delete all tables in the schema"
@pomazanbohdan pomazanbohdan mentioned this issue Jan 9, 2019
Closed
@pomazanbohdan pomazanbohdan changed the title Add a button in the options "Untrek all relationships and tables in the scheme" Add a button in the options "Untreсk all relationships and tables in the scheme" Jan 9, 2019
@pomazanbohdan
Copy link
Author

Oh my.
"Reset" - work.

I had a problem when I dropped tables without a metadata reset, then it did not work after.

@pomazanbohdan pomazanbohdan changed the title Add a button in the options "Untreсk all relationships and tables in the scheme" "Reset" not work after manual drop tables "public" Jan 9, 2019
@pomazanbohdan
Copy link
Author

pomazanbohdan commented Jan 9, 2019 •
edited
Loading

And if I make a change in the structure of the database that is critical for the database, without a prior "reset", then there is no way to work "Reset"

@praveenweb
Copy link
Member

@Pomazan-Bogdan - Have you tried Reset Metadata option under /console/metadata page? It will untrack all metadata that Hasura tracks. You can then manually add tables/relationships again.

@pomazanbohdan
Copy link
Author

  1. I change structura DB
  2. go manual /console/metadata and RESET
  3. All tables untrack
  4. Profit

But if i after step 1 go to menu "Data", redirect to login page

hasura-bot pushed a commit that referenced this issue Nov 18, 2024
@jberryman @hasura-bot
ENG-1287 remove metadata copy from SQL artifact (#1348)
426a834 
<!-- The PR description should answer 2 important questions: -->

### What

Remove copies of metadata from SQL artifacts:

Resulting in **19% smaller artifact** for chinook, **17% faster
runtime**.
Customer metadata with multiple subgraphs will show more dramatic
effect.

There was a separate copy of the metadata stored for each subgraph in
the sql "catalog". From the point of view of MBS we were serializing 2+N
copies of the same metadata which bloats artifacts and is very slow.

Additionally the usage sites became confusing because you had multiple
identical (we assume) copies of metadata in scope at the same time.

Instead we reconstruct the original Catalog type before use, because
it's required for the Datafusion impls

### How

convert to a different type for serialization, re-hydrate in body of sql
code

V3_GIT_ORIGIN_REV_ID: 0e7e35255cfe8fe01ea328a1d7cb96db0e2dd726
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pomazanbohdan @praveenweb