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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wasn't the previous behavior to attempt to load the view if the HEAD request is not supported? I think it would be safer to check
V1_LOAD_VIEWand use that if it is supported before returning false.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we might actually need to fall back to loading the view as we did previously. Also btw the same issue applies for
namespaceExistsandtableExistsas those three are all now doing a HEAD request. We might need something likeThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have some inconsistency about how we're handling this. The
listViewstakes the same approach as what I have here, which also aligns with ourDEFAULT_ENDPOINTS, so it's strange that it would call load view, but list view would return nothing.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for fallback to older logic as @nastra suggested. I sent #12294 with some tests.
I decided to skip Iceberg 1.8.0 in Tirno due to this endpoint's issue and S3 strong integrity checksum issue #12264.