Use the actual partition name from the storage in syncing partition metadata #22484
+155
−10
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
The canonical partition name built from the column name and values of the partition may differ from the actual storage location of the partition. This can lead to inconsistencies when syncing partition metadata, like identifying a partition to add/remove when there is actually nothing to be done.
Rely on the partition name from the storage location for identifying the partitions to sync via the
sync_partition_metadata
procedure call.Additional context and related issues
This fix applies specifically where there is a partition name case sensitive variation between the canonical name and the storage location of the partition.
See
io.trino.plugin.hive.TestHive3OnDataLake#testSyncPartitionCaseSensitivePathVariation
for details.Follow-up from #21168
Release notes
(x) Release notes are required, with the following suggested text: