Daniel Mewes

@fkollmann Thanks for sharing your script. It still appears to be working for me. What is the Python version that comes with SLES 12? (`python --version`)

:+1:

I'm moving this into the 2.3.x milestone, so that we can release it as a minor update before RethinkDB 2.4.

@foxx @orokusaki Have you had a chance to try out the driver from branch `dalanmiller_aiter_and_anext` in the meantime?

@jilen Yes, renaming the `$reql_temp_index$_...` indexes to their proper names (without the `$reql_temp_index$` prefix) should work and complete the index migration.

It's very likely that the original index rebuild failure was caused by the table still being backfilling. I think we should put a `table.wait()` into the index rebuild script. Probably...

We added the `table.wait()` to the import/restore scripts, but not to `index-rebuild`. I think we should do it in `index-rebuild` as well.

This appears to be due to `ApproximateArrivalTimestamp` being expressed as a floating point number (in seconds) in kinesalite, while KCL requires it to be an integer (I believe in milliseconds)....

Now wondering if this might actually be caused by https://github.com/aws/aws-sdk-java-v2/issues/1023 in the AWS SDK...

Thanks for reporting this @antoniocanas . Pinging @dalanmiller