Closed pdbossman closed 1 month ago
This is probably a consequence of #103, see my comment there about using anything else than 1 for scanSegments
: https://github.com/scylladb/scylla-migrator/issues/103#issuecomment-1959192238.
I am closing this issue since it was likely due to the schema inference, which we do not perform anymore.
Source dynamodb, target scylla alternator.
Using higher concurrency settings on source with very little data errors out (no data copied): config.yaml scanSegments: 256 maxMapTasks: 8
Same source/target, all other parameters the same - but set scanSegments and maxMapTasks to 1: scanSegments: 1 maxMapTasks: 1
No errors, copies the row.