[
https://issues.apache.org/jira/browse/HADOOP-15006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320399#comment-16320399
]
Steve Loughran commented on HADOOP-15006:
-----------------------------------------
* you are going to have to handle the fact that its only on the final post
where things are manifest later, with a separate process/host doing the final
POST. that's when any info would have to be persisted to DDB
* There is a length http header on encrypted files; these could be scanned to
repopulate the s3guard tables
One thing to consider is that posix seek() lets you do a relative-to-EOF seek.
Could we offer that, or at least an API call to get the length of a data
source, in our input stream. And then modify the core file formats (Sequence,
ORC, Parquet...) to use the length returned in the open call, rather than a
previously cached value?
> Encrypt S3A data client-side with Hadoop libraries & Hadoop KMS
> ---------------------------------------------------------------
>
> Key: HADOOP-15006
> URL: https://issues.apache.org/jira/browse/HADOOP-15006
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs/s3, kms
> Reporter: Steve Moist
> Priority: Minor
> Attachments: S3-CSE Proposal.pdf
>
>
> This is for the proposal to introduce Client Side Encryption to S3 in such a
> way that it can leverage HDFS transparent encryption, use the Hadoop KMS to
> manage keys, use the `hdfs crypto` command line tools to manage encryption
> zones in the cloud, and enable distcp to copy from HDFS to S3 (and
> vice-versa) with data still encrypted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
