Repository navigation
fix(pipeline): skip absent-table records during schema pre-warm - #349
Merged
Merged
Conversation
A routing reload pre-warms every source table it names. The engine writes a new source's routing and creates its table together. The pre-warm can miss the table and record it as absent. Every batch for that source then went to the default table until the entry expired. A pre-warm now skips recording absent tables. The source's first batch resolves the table, waiting in the pending-schema buffer like any unresolved table. A table that never appears still falls back once a batch asks for it.
The default table is never marked as missing. Its pre-warm result still goes to the event loop. A missing default table triggers a warning at boot and when its first row arrives.
|
Released in v1.18.73 -- https://github.com/hyperi-io/dfe-loader/releases/tag/v1.18.73 |
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.
A routing reload pre-warms every source table it names. The engine writes a new source's routing and creates its table together. The pre-warm can miss the table and record it as absent. Every batch for that source then went to the default table until the entry expired.
A pre-warm now skips recording absent tables. The source's first batch resolves the table, waiting in the pending-schema buffer like any unresolved table. A table that never appears still falls back once a batch asks for it.