fix(firebolt-schema-builder): better fallback to projection type resolution #1800
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.
Description:
Previously a fresh setup of S3 source -> Firebolt sink would lead to an error by default due to the internal
_meta/flow_truncated
field's type not being resolved.In this PR I'm trying to ensure we try to resolve the type via the projection whenever we're not able to do so with the explicit mapping from the Shape object.
Workflow steps:
Now setting up an S3 source and Firebolt sink should work by default.
Documentation links affected:
N/A
Notes for reviewers:
Added relevant tests to illustrate and test the issue.
This change is