Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
When doing a copy, S3A always uses encryption configuration of the filesystem, rather than the source object. This behaviour may not have been intended, as in `RequestFactoryImpl.copyEncryptionParameters()` it does copy source object encryption properties here , but a missing return statement means it ends up using the FS settings anyway.
Proposed:
- If the copy is called by rename, always preserve source object encryption properties.
- For all other copies, use current FS encryption settings.