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

Bug/persist docs/performance #616

Merged
merged 8 commits into from
Mar 19, 2024
Merged

Bug/persist docs/performance #616

merged 8 commits into from
Mar 19, 2024

Conversation

benc-db
Copy link
Collaborator

@benc-db benc-db commented Mar 19, 2024

Copied from #615

Resolves #608

Description
It appears that incremental catalog generation actually takes longer in databricks than generating the catalog all at once. This appears to be partially due to the column comment queries that are required while building the catalog. Running one query to build this all at once is faster once there is more than roughly 5 models. Given how small this break even number, and how infrequently it would be beneficial, it's probably a lot easier to simply turn off incremental catalog generation.

Checklist

  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.

@benc-db benc-db merged commit c3781f8 into main Mar 19, 2024
6 checks passed
@benc-db benc-db mentioned this pull request Mar 19, 2024
3 tasks
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

Successfully merging this pull request may close these issues.

decrease in job performance for dbt docs generate
2 participants