Repository navigation
v0.1.6
v0.1.6
Changes
- Upgrade the LambdaDB Go SDK to v0.4.0 and support the current collection API: HTTP 201 creation, wrapped collection metadata, and no
collectionStatuspolling. - Preserve SDK-managed signed bulk-upload headers and
Content-Type: application/json, with regression coverage for upload retries, completion retries, and storage 412 responses. - Fix completed-checkpoint resume: rerunning a completed migration no longer replays the final source page or inflates accepted-record counts.
- Retain validation samples in checkpoints so failed post-migration validation can be retried without uploading the documents again. Checkpoint files now use owner-only permissions.
- Expand regression coverage for partial-write recovery, empty terminal pages, completed reruns, validation retries, restart, and checkpoint cleanup.
Upgrade notes
- This version targets the current LambdaDB API supported by Go SDK v0.4.0. Deployments that still expose the older collection creation/status contract need an API upgrade first.
- Checkpoints add optional
sourceDoneandvalidationSamplesfields. Older checkpoint files remain readable and resume from their saved cursor. - A checkpoint from an already completed migration created by an older CLI has no completion marker. Use
--migration.restartfor a fresh run; completion is not inferred from document counts. - Use
--migration.restartto migrate new source data after a completed run. - Validation-enabled migrations store bounded sample documents locally. A completed checkpoint without saved samples requires restart for sample validation, or
--migration.validation-sample-size=0for count-only validation.
Full changes: v0.1.5...7256838