perf(ingest/redshift): limit copy lineage #11662
Merged
Conversation
This file contains 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
This limits it to a max of 20 entries per table, which means that we can't get overwhelmed by lineage entries for tables with ultra-high traffic.
hsheth2
changed the title
github-actions
bot
added
the
ingestion
mayurinehate
approved these changes
Oct 18, 2024
| c.file_name AS filename, | ||
| ROW_NUMBER() OVER ( | ||
| PARTITION BY sti."schema", sti."table" | ||
| ORDER BY si.start_time ASC |
There was a problem hiding this comment.
Should we use DESC in favour of getting latest rows ?
mayurinehate
added
the
merge-pending-ci
sleeperdeep
pushed a commit
to sleeperdeep/datahub
that referenced
this pull request
Dec 17, 2024
Co-authored-by: Mayuri Nehate <[email protected]>
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.
This limits it to a max of 20 entries per table, which means that we can't get overwhelmed by lineage entries for tables with ultra-high traffic.
Checklist