jiangxt2 opened a new issue, #13720: URL: https://github.com/apache/gravitino/issues/13720
### What would you like to be improved? Gravitino provides an Iceberg REST service for external clients, but its test suite does not currently include a Gravitino-owned end-to-end test for Daft reading and writing existing Iceberg tables. Regressions in service configuration, catalog loading, or table commit handling could break this integration without being detected by Gravitino CI. The related Ray Data contract-test work is tracked in [#13323](https://github.com/apache/gravitino/issues/13323) and [#13325](https://github.com/apache/gravitino/pull/13325). [#9264](https://github.com/apache/gravitino/issues/9264) tracks integration tests in the Daft repository; this proposal covers regression testing within Gravitino. ### How should we improve? Add a Gravitino-owned integration test using Daft’s native runner and a compatible PyIceberg version against a real Gravitino Iceberg REST service. The test should cover: - Loading an existing table through PyIceberg and reading it with `daft.read_iceberg()`, including an empty table. - Appending data with `DataFrame.write_iceberg()`. - Reloading the table and verifying row counts, field order, values, and filtering results. - Cleaning up test metadata, temporary warehouse data, and service configuration. Use an isolated dependency environment and a dedicated test entry point in Gravitino CI. Keep the initial scope limited to existing-table reads and append writes through Iceberg REST. Daft Catalog discovery, GVFS, credential vending, and changes to production APIs are outside this issue. -- 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]
