Julien Richard-Foy

Thank you @javierfvargas for opening the PR! I didn’t have a look at the implementation yet but it seems there is a test failure: https://github.com/julienrf/play-json-derived-codecs/actions/runs/11803446878/job/33012046622?pr=97#step:6:126 It looks like the discriminator...

Hello, thank you for explaining the issue. I agree that 140 seconds is way too long. A workaround could be to manually set `versionPolicyPreviousVersions` so that it is not computed...

I think the infinite recursion comes from the fact that when deriving the `Writes[Base]` we try to find if there is an existing `Writes[Foo]` to use it, but that one...

The first step to move forward is to publish our fork of `spark-cassandra-connector`, so that the Migrator can use it directly instead of building it from source. I suggest creating...

I am closing this issue since scylladb/spark-scylladb-connector#6 is (almost) done, and the next steps are tracked by the following issues: - scylladb/spark-scylladb-connector#13 - scylladb/spark-scylladb-connector#14

Done in [c2835e5](https://github.com/scylladb/scylla-migrator/pull/182/commits/c2835e55b53e29585c1a92f4c1e47aeb285d4517).

What was the cluster configuration? How many worker nodes did you have? What was the migration configuration?

I believe you found the right workaround: the cleanup does not happen by default when jobs are running. In our case, since our job is a long-running job this is...

The problem boils down to the fact that for _every_ item transferred by the migrator, the DynamoDB connector prints a line in the logs: https://github.com/awslabs/emr-dynamodb-connector/blob/07391dd0937bdbb20b86ec79444798df11b0711f/emr-dynamodb-hadoop/src/main/java/org/apache/hadoop/dynamodb/DynamoDBClient.java#L242 A possible solution is to...

I just submitted #171 as a fix. Note that when we will fix #132, we will have a chance to change the code of the `DynamoDBClient` itself and fix the...