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

High Query Cost using Bigquery TABLE_STORAGE #14433

Closed
ayush-shah opened this issue Dec 19, 2023 · 0 comments · Fixed by #14507
Closed

High Query Cost using Bigquery TABLE_STORAGE #14433

ayush-shah opened this issue Dec 19, 2023 · 0 comments · Fixed by #14507
Assignees
Labels
enhancement New feature or request profiler

Comments

@ayush-shah
Copy link
Member

ayush-shah commented Dec 19, 2023

We have identified the issue related to Bigquery profiling over table storage for fetching the system level tags like no. of rows, sizeInBytes, creation time, col names and col count.

Instead of using table storage from information schema which can be huge, we can use __TABLES__ to get metadata for that table.

ref: https://openmetadata.slack.com/archives/C02B6955S4S/p1702021485941039

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request profiler
Projects
No open projects
Status: Done
1 participant