5 ms·
This was a problem with data lakes / analytics. Small inconsistencies would trash runs; that problem now goes away and removes a lot of janky half-fixes to work
by QuinnyPig 6y ago
This was a problem with data lakes / analytics. Small inconsistencies would trash runs; that problem now goes away and removes a lot of janky half-fixes to work around the issue.
For most common use cases it's not really an issue.
- FridgeSeal 6y agoOf course the real issue there is those tool treating S3 as something it's not (a filesystem) and building things on it with the expectation of certain guarantees that it explicitly didn't provide before now. I dig the feature (strong consistency) but in some ways it just enables tools that were abusing it to just do so more easily.
- staticassertion 6y agoLike RedShift? AWS uses S3 as a database, seems reasonable that their customers would.
- FridgeSeal 6y agoThat doesn't mean it blindly "mounts" it as a disk and attempts to use it as a filesystem. They're almost certainly using it in a manner that is aware of the specificities of how S3 works.
- foxhop 6y agoWhat if the blind mount works 99.9% of the time? I knew what I was doing was risky but well with in my tolerance for pain. Now that we have a strong consistency my code is fixed. That's pretty impressive.
- Decker87 6y agoIsn't that the point? To provide some useful functionality for others to build on (and pay for)?