Repository navigation
perf(lineage): analyse traced columns against only referenced relations - #877
Merged
Merged
Conversation
…relations Rich column lineage rebuilt the Polyglot schema for the whole project for every analysed model and handed all of it to analyze_query, so a column trace cost (models traced x project schema). Build the Polyglot table entries once per invocation and pass each model only the relations it references. Output is unchanged. Refs: CHI-433
Add rich column traces upstream from the lattice rollup (text) and downstream from the hub (JSON) to the 3,000-model inspection guard with wall-time, peak-RSS and output-line ceilings. Refs: CHI-433
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
sqb lineage <model>.<column>rebuilt the whole-project analyser schema for every traced model and passed all of it to the analyser, so cost grew with (models traced x tables in the project). On the 3,000-model diamond benchmark an upstream column trace took ~67 s.Changes
__ref/__source/__seed, macro-expanded SQL), in the same sorted order.Verification
make test,make check-ci, performance target under 4 GiB; one independent review.