Fix: use correct check for column prop in column schema #1347
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
In dlt <= 0.4.9
I would construct schemas like so:
And this would work fine. However in 0.4.10, there is an irrecoverable error that took down our pipelines leveraging this technique. This is due to the check for column props which would detect multiple
dedup_sort
hints in the following schema (and in all schemas) incorrectly. There is no dedup_sort hint unless there is a truthy value that is one of asc or descI have fixed this check and verified my pipelines are working again.