stevenzwu commented on code in PR #12584:
URL: https://github.com/apache/iceberg/pull/12584#discussion_r2586873349
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -3405,6 +3513,66 @@ components:
allOf:
- $ref: '#/components/schemas/ScanTasks'
+ QueryEventsRequest:
+ type: object
+ properties:
+ page-token:
Review Comment:
I asked Gemini
```
is page-token or continuation-token a better name for the checkpoint/resume
point for changelog consumption pattern for web services?
```
Here is what I got
```
Continuation-token is the better and more accurate name for the
checkpoint/resume point in a changelog consumption pattern.
It is the standard and preferred term in modern API design, especially when
dealing with feeds, streams, or large, unbounded datasets like change logs.
The Core Difference
The distinction lies in the concept of bounded vs. unbounded data:
Page-token: Best for results of a search query or a filtered list. The
dataset is finite at the time of the query.
Continuation-token: Best for event streams, change feeds, or logs. The
dataset is constantly growing and functionally infinite, and the client wants
to know where to continue fetching the new records. Major services like Azure
Cosmos DB (for change feeds) and various feed APIs use this term.
Using continuation-token clearly signals to developers that this is a
durable checkpoint to be stored and used to resume an ongoing process, often
without a fixed or known end.
```
Gemini linked source to Cosmos database.
https://docs.azure.cn/en-us/cosmos-db/nosql/change-feed-pull-model
The events endpoint is designed for change feed consumption. Hence, I
thought `continuation-token` is probably more accurate.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
