[1.10.x] Core: Fix planning request/response validations #14566
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The OpenAPI spec says in https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml#L618-L624 that if no snapshotId is provided, the server can select the latest snapshot in the table's main branch. However, currently the request always requires to set either the `snapshotId` or the `startSnapshotId`/`endSnapshotId`
The OpenAPI spec indicates in https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml#L3376-L3384 that a `completed` planning result can have a `planId`
huaxingao
approved these changes
Nov 12, 2025
Contributor
Author
|
thanks for the review @huaxingao |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This backports #14561 and #14562 to 1.10.x