Reading up on S3’s consistency model (https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html#ConsistencyModel), I see that the list after create is actually eventual consistent only. Is this going to cause problem with TileDB’s current implementation? For instance, it looks like when it’s reading a fragment for a column attribute it looks like it would write the fragments with timestamps in their names. Thus, I’d imagine that you’ll need to do a “list” operation in order to see what’s the latest fragment to read.
Say if I have job A that update an array and job B depends on job A’s data, is there a case where job B would not be able to read the data produced by A since the s3 listing would not have A’s fragments show up?