Details
-
Sub-task
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
2.8.0
-
None
-
None
Description
Looking at traces of work, there's invariably a PUT of a _SUCCESS at the end, which, with disk output, adds the overhead of creating, writing to and then reading a 0 byte file.
With a lazy create, the creation could be postponed until the first write, with special handling in the startUpload() operation to return a null stream, rather than reopen the file. Saves on some disk IO: create, read, delete
Attachments
Issue Links
- is related to
-
HADOOP-13293 add a special 0 byte input stream for empty blobs
- Open