[BUGFIX] Resolve partition deleting bug in insert_overwrite mode #139
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.
Bug
Currently boto3 is able to accidentally skip deleting of some partitions during incremental build in
insert_overwrite
mode.Why it's important
Adapter can skip deleting of some partitions before inserting from rows temporary table. New data will appended for undeleted partitions but not overwrited.
This bug prevents me from using this adapter in my pipelines.
What wrong with code
Logic of receiving partition details is poor.
get_partitions()
function should take into accountNextToken
parameter (a continuation token, if this is not the first call to retrieve these partitions).How I fixed this bug
I added loop to be sure that boto3 will find and delete target partition. I got inspiration from
awswrangler
library, example of get_partitions usage.