Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/18979
Currently *nobody should be using s3a:// at the the temp file destination*,
which is the same as saying "nobody should be using s3a:// as the direct
destination of work", not without a special committer (Netflix, IBM's stocator,
...) or without something to give S3 list consistency. Because today, task
commit relies on a list & rename of all files in the task attempt dir, and if
you don't get list consistency, you can miss out on files. If you ever hear
anyone complaining "it takes too long to commit to s3" then they are using it
this way. Tell them to use a consistency layer or to stop it :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
