jackye1995 commented on code in PR #9717:
URL: https://github.com/apache/iceberg/pull/9717#discussion_r1495056159
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -2513,6 +2536,7 @@ components:
- $ref: '#/components/schemas/RemovePropertiesUpdate'
- $ref: '#/components/schemas/SetStatisticsUpdate'
- $ref: '#/components/schemas/RemoveStatisticsUpdate'
+ - $ref: '#/components/schemas/AppendDataFilesUpdate'
Review Comment:
> The table API commits to the table every time it is called, but I think
that the value of an API that can post new data files is that you don't
necessarily need to commit every time.
+1000
I was planning to bring this up as an extension after the initial change is
merged, because to me this use case can be supported by:
1. support asynchronous update, where the UpdateTable returns a 202 accepted
with a handle to check for update progress, and another API to check for
progress completion status.
2. support batch commit, where a flag is added to say the specific
UpdateTable request can be batch-committed instead of being immediately
committed. As of today the REST specification does not really enforce a 1:1
relationship between the UpdateTable call vs the transaction in the table,
that's why I went with this line of thought.
If we go with a new API, do you have any initial thoughts on what it could
look like?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org
