Airbyte ingestion improvements #513
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
…estamp, row UUID) to make storage/querying more efficient. This stops Splitgraph from thinking that the chunks we produce are overlapping because the UUIDs are effectively random (the ideal solution would be changing the storage format and somehow noting this during commit -- 0b139a7 has more background on why this was disabled, but here, as we know the chunks aren't overlapping, we could manually mark them?)
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.
When storing Airbyte raw tables, change their PK to be (ingestion timestamp, row UUID) to make storage/querying more efficient.
This stops Splitgraph from thinking that the chunks we produce are overlapping because the UUIDs are effectively random (the ideal solution would be changing the storage format and somehow noting this during commit -- 0b139a7 has more background on why this was disabled, but here, as we know the chunks aren't overlapping, we could manually mark them?)