Github user NicoK commented on the issue:
https://github.com/apache/flink/pull/5624
Unfortunately, this is not entirely under our control, since we rely on the
underlying `FileSystem` implementation. I can probably reduce some parts of the
tests that may lead to eventual consistent operations, but looking through
[S3's data consistency
model](https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html#ConsistencyModel),
I figure we still (at least) have to deal with these scenarios:
> - A process writes a new object to Amazon S3 and immediately lists keys
within its bucket. Until the change is fully propagated, the object might not
appear in the list.
> - A process deletes an existing object and immediately lists keys within
its bucket. Until the deletion is fully propagated, Amazon S3 might list the
deleted object.
This could, however, be handled on a case-to-case basis and I could try to
improve the tests in this regard.
---
