You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LoadTableReponse appears to be a superset of CommitTableResponse, and the subsequent code that uses the response only uses fields in the latter, but it is a little misleading for the casual reader who may expect all the data from LoadTableResponse to be available.
Willingness to contribute
I can contribute a fix for this bug independently
I would be willing to contribute a fix for this bug with guidance from the Iceberg community
I cannot contribute a fix for this bug at this time
The text was updated successfully, but these errors were encountered:
Apache Iceberg version
None
Query engine
None
Please describe the bug 🐞
This is a little nit-picky, but the Iceberg REST spec defines the response of the UpdateTable (commit) operation to be
CommitTableResponse
iceberg/open-api/rest-catalog-open-api.yaml
Line 1004 in d402f83
But the code implementing UpdateTable (commit) uses
LoadTableResponse
to hold the results of the operation.iceberg/core/src/main/java/org/apache/iceberg/rest/RESTTableOperations.java
Line 158 in 6c05f35
LoadTableReponse
appears to be a superset ofCommitTableResponse
, and the subsequent code that uses the response only uses fields in the latter, but it is a little misleading for the casual reader who may expect all the data fromLoadTableResponse
to be available.Willingness to contribute
The text was updated successfully, but these errors were encountered: