jerryshao opened a new issue, #11134: URL: https://github.com/apache/gravitino/issues/11134
## Describe the subtask `listTables`, `listNamespaces`, and `listViews` do not accept `pageToken` or `pageSize` query parameters, which are part of the Iceberg REST OpenAPI spec. Large namespaces return the full result set in a single response, holding the entire list in server heap and serializing it as a large JSON response. Clients cannot iterate incrementally. **Files:** - `iceberg/iceberg-rest-server/src/main/java/org/apache/gravitino/iceberg/service/rest/IcebergTableOperations.java:114-135` - `iceberg/iceberg-rest-server/src/main/java/org/apache/gravitino/iceberg/service/rest/IcebergNamespaceOperations.java:91-120` - `iceberg/iceberg-rest-server/src/main/java/org/apache/gravitino/iceberg/service/rest/IcebergViewOperations.java:86-110` - `iceberg/iceberg-common/src/main/java/org/apache/gravitino/iceberg/common/ops/IcebergCatalogWrapper.java:144-147, 228-230` **Fix (two-stage):** - **Stage 1** (spec conformance): Accept `pageToken`/`pageSize`, fetch full list, sort deterministically, return sliced results with a next-page token. Sets a default and maximum page size. - **Stage 2** (scalability): Bypass `CatalogHandlers.list*` and use native backend pagination — keyset pagination for JDBC, `get_tables_max` for HMS. Stage 1 alone is sufficient for spec conformance. Stage 2 is the real scalability fix and can ship separately. ## Parent issue https://github.com/apache/gravitino/issues/11131 -- 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]
