dentiny opened a new issue, #1251:
URL: https://github.com/apache/iceberg-rust/issues/1251
### Is your feature request related to a problem or challenge?
It's possible to have large number of namespace and tables, with query
taking long time listing these large entities. I'm wondering if it's possible
and good to provide pagination functionality to list operations.
Interface proposal:
```rs
/// Pagination parameters for listing namespaces
#[derive(Debug, Clone)]
pub struct PaginationOptions {
/// Maximum number of items to return
pub max_results: usize,
/// Token for continuing a previous listing
pub page_token: Option<String>,
}
/// Result of a paginated namespace listing
#[derive(Debug)]
pub struct PaginatedList<T> {
/// The actual items returned
pub items: Vec<T>,
/// Token for retrieving the next page of results
pub next_page_token: Option<String>,
}
/// List namespaces with pagination support
async fn list_namespaces_paginated(
&self,
parent: Option<&NamespaceIdent>,
pagination: PaginationOptions,
) -> IcebergResult<PaginatedList<NamespaceIdent>>;
/// List tables with pagination support
async fn list_tables_paginated(
&self,
namespace: &NamespaceIdent,
pagination: PaginationOptions,
) -> IcebergResult<PaginatedList<TableIdent>>;
```
### Describe the solution you'd like
_No response_
### Willingness to contribute
I can contribute to this feature independently
--
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.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
