saidixith002 opened a new pull request, #257:
URL: https://github.com/apache/polaris-tools/pull/257
## Summary
- Adds `polaris-synchronizer/manual-test/`: a self-contained
docker-compose setup that brings up a source and target Apache Polaris instance
(in-memory metastore, no
Postgres/S3 needed) to manually exercise `sync-polaris` end-to-end.
- Source and target share a single FILE storage volume mounted at the same
path, so a full sync (namespace/table content included) actually succeeds —
this lets both the full
sync and a `--skip-iceberg-content` sync be run back-to-back in one
session and compared.
- Documents `--skip-iceberg-content` in the main
`polaris-synchronizer/README.md` (previously undocumented there) and links to
the new harness under a "Testing Locally"
section.
- Ignores the harness's generated `seed/credentials.json` (bind-mounted
volume, persists across `docker compose down`).
## Related
Depends on / references #256. The manual-test walkthrough documents and
exercises `--skip-iceberg-content`, which is only implemented on that branch —
until
#256 merges, following the harness's `--skip-iceberg-content` steps
against a jar built from `main` won't work, since the flag doesn't exist yet on
`main`. Everything else
(docker-compose harness, seeding, full-sync steps) works independently of
#256.
## Test plan
- [x] `docker compose up --build -d` from
`polaris-synchronizer/manual-test/` — source, target, and `polaris-init` all
come up healthy.
- [x] Ran `create-omnipotent-principal` against source (read-only) and
target (`--write-access`).
- [x] Ran `sync-polaris` with `--skip-iceberg-content` —
catalog/catalog-role/grant sync succeeds, target namespaces empty.
- [x] Re-ran `sync-polaris` without the flag — namespace/table sync
succeeds (shared storage), target ends up with `test_ns`/`test_table`.
- [x] Verified via `curl` against target's management/catalog APIs at each
step.
--
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]
