You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "richiebachala (via GitHub)" <gi...@apache.org> on 2026/10/04 03:48:47 UTC

Re: [I] Catalog Conformance Testing Suite [iceberg-go]

richiebachala commented on issue #1691:
URL: https://github.com/apache/iceberg-go/issues/1691#issuecomment-5976285627

   I'm interested in contributing to catalog conformance testing after my first iceberg-go issue is complete. A small first slice might extract one common REST catalog behavior into a shared, catalog-agnostic test harness, with existing implementations opting in. Is there a particular operation or test boundary maintainers would prefer? I'm not claiming this for simultaneous implementation; I want to align scope before picking it up.


-- 
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-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org