Since NXP-29292, S3DirectBatchHandler uses AWS TransferManager
However the new code deletes the "hack" to handle Multipart upload where the object must be rename to have a key which equals the ETag. Otherwise it produces this exception when trying to create a Nuxeo document which has a reference on the S3 object
Caused by: java.io.IOException: Invalid S3 object digest, expected=4abbd17776541a3151422dc2c8136e58-3 actual=3b4a1541bd9242c00cfb212d524619e7 at org.nuxeo.ecm.core.storage.sql.S3BinaryManager$S3FileStorage.fetchFile(S3BinaryManager.java:677) ~[nuxeo-core-binarymanager-s3-10.10-HF29.jar:?] at org.nuxeo.ecm.core.blob.binary.CachingBinaryManager.getFile(CachingBinaryManager.java:182) ~[nuxeo-core-api-10.10-HF29.jar:?] at org.nuxeo.ecm.core.blob.binary.LazyBinary.getFile(LazyBinary.java:67) ~[nuxeo-core-api-10.10-HF29.jar:?] at org.nuxeo.ecm.core.blob.binary.LazyBinary.getStream(LazyBinary.java:60) ~[nuxeo-core-api-10.10-HF29.jar:?] at org.nuxeo.ecm.core.blob.binary.BinaryBlob.getStream(BinaryBlob.java:65) ~[nuxeo-core-api-10.10-HF29.jar:?] at org.nuxeo.ecm.platform.mimetype.service.MimetypeRegistryService.getMimetypeFromBlob(MimetypeRegistryService.java:305) ~[nuxeo-core-mimetype-10.10.jar:?] at org.nuxeo.ecm.platform.mimetype.service.MimetypeRegistryService.getMimetypeFromBlobWithDefault(MimetypeRegistryService.java:334) ~[nuxeo-core-mimetype-10.10.jar:?] at org.nuxeo.ecm.platform.mimetype.service.MimetypeRegistryService.getMimetypeFromFilenameWithBlobMimetypeFallback(MimetypeRegistryService.java:366) ~[nuxeo-core-mimetype-10.10.jar:?] at org.nuxeo.ecm.platform.mimetype.service.MimetypeRegistryService.updateMimetype(MimetypeRegistryService.java:380) ~[nuxeo-core-mimetype-10.10.jar:?] at org.nuxeo.ecm.platform.filemanager.service.FileManagerService.checkMimeType(FileManagerService.java:151) ~[nuxeo-platform-filemanager-core-10.10.jar:?] at org.nuxeo.ecm.platform.filemanager.service.FileManagerService.createOrUpdateDocument(FileManagerService.java:266) ~[nuxeo-platform-filemanager-core-10.10.jar:?]
- is caused by
-
NXP-29292 Use AWS TransferManager in S3DirectBatchHandler
- Resolved
- is related to
-
NXP-29478 Fix S3 direct upload for files larger than 5GB
- Resolved
-
NXP-29319 Allow using arbitrary file keys in S3
- Resolved
-
NXP-29496 Fix S3 Direct Upload for little files (SSE-KMS)
- Resolved
- Is referenced in