Julien Richard-Foy
Julien Richard-Foy
I am closing this issue since we were not able to reproduce it and we had no news for some time. We can re-open it if someone can confirm that...
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.
@pdbossman Thank you for the detailed report. I confirm that I reproduced the issue when the credentials are provided via `~/.aws/credentials` on the Spark worker node. It seems they are...
@pdbossman I was able to use the AWS profile credentials with the following change: https://github.com/julienrf/scylla-migrator/tree/aws-credentials Could please let me know if that fixes your issue?
Unfortunately, the PR contains a lot of changes, but in my opinion this is still the best approach to go for now. I’ve also considered using reflection-based approaches to access...
Superseded by #173
I believe this issue has been fixed since we don’t infer the table schema anymore. Please let me know if you are still blocked.
Commenting on this issue instead of creating a new one because this is related to the testing infrastructure. Currently, our testing infrastructure recreates the AWS stack (S3 and DynamoDB) in...
Regarding this point: - we can trigger the workflow only under some conditions: e.g. one of the maintainers posts a comment “Test on AWS” on the PR - by default,...