[
https://issues.apache.org/jira/browse/HADOOP-15224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-15224:
------------------------------------
Release Note: The option fs.s3a.create.checksum.algorithm allows checksums
to be set on file upload; It supports the following values: 'CRC32',
'CRC32C', 'SHA1', and 'SHA256'. A future release will also support "none".
(was: The option fs.s3a.create.checksum.algorithm allows checksums to be set
on file upload; It supports the following values: 'CRC32', 'CRC32C',
'SHA1', and 'SHA256'
)
> S3A: Add option to set checksum on S3 objects
> ---------------------------------------------
>
> Key: HADOOP-15224
> URL: https://issues.apache.org/jira/browse/HADOOP-15224
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Assignee: Raphael Azzolini
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.5.0, 3.4.2
>
>
> The option fs.s3a.create.checksum.algorithm allows checksums to be set on
> file upload; It supports the following values:
> 'CRC32', 'CRC32C', 'SHA1', and 'SHA256'
> * This can protect against corruption of data even before uploading
> commences, and enables support for buckets with S3 Object Lock activated.
> * Third party stores may not support these checksum algorithms, or support a
> limited subset
> * Cryptographically strong hashes, here SHA1 and SHA256, are alway slower
> than simple CRC checksums.
> For verifying data is not tampered with before data upload, CRC32C should
> suffice
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
