Problem
The only REST test fixture today is an in-memory mock. It does not persist data, does not return real table schemas/paths, and does not support commit, so the RESTCatalog client cannot be exercised end to end (metadata + append write + commit + read).
Proposal
Add a small dev crate (paimon-rest-server, publish = false) that serves the Paimon REST protocol over a real FileSystemCatalog:
- config + database/table metadata CRUD;
- append write + commit (the commit endpoint persists the posted snapshot via
SnapshotManager) + read back;
- column-level
alter table.
Because the server and client share the same local warehouse, and the wire format mirrors Java Paimon, the same warehouse can be round-tripped with a Java reader/writer. A CI job runs the crate's e2e tests.
This depends on the column-level alter table work tracked separately.
Problem
The only REST test fixture today is an in-memory mock. It does not persist data, does not return real table schemas/paths, and does not support commit, so the
RESTCatalogclient cannot be exercised end to end (metadata + append write + commit + read).Proposal
Add a small dev crate (
paimon-rest-server,publish = false) that serves the Paimon REST protocol over a realFileSystemCatalog:SnapshotManager) + read back;alter table.Because the server and client share the same local warehouse, and the wire format mirrors Java Paimon, the same warehouse can be round-tripped with a Java reader/writer. A CI job runs the crate's e2e tests.
This depends on the column-level alter table work tracked separately.