[ 
https://issues.apache.org/jira/browse/HADOOP-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416121#comment-17416121
 ] 

Steve Loughran commented on HADOOP-17912:
-----------------------------------------

# mixing encryption options in the same bucket has proved a PITA in the s3a 
connector, especially in testing. Is this really, really needed? If so: may 
need to do test runs while no other test cases are running against the same 
store
# are these secrets going to be something you'd want to propagate with 
delegation tokens, so that in, say, a spark job distributed to a cluster, it'd 
go with them?
# do you need the secrets for list/HEAD calls? As it's that, the need for 
secrets to call HEAD, which are a source of extreme pain: clients can't even 
call getFileStatus() without the right secrets

> ABFS: Support for Encryption Context
> ------------------------------------
>
>                 Key: HADOOP-17912
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17912
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 3.3.1
>            Reporter: Sumangala Patki
>            Assignee: Sumangala Patki
>            Priority: Major
>
> Support for customer-provided encryption keys at the file level, superceding 
> the global (account-level) key use in HADOOP-17536.
> ABFS driver will support an "EncryptionContext" plugin for retrieving 
> encryption information, the implementation for which should be provided by 
> the client. The keys/context retrieved will be sent via request headers to 
> the server, which will store the encryption context. Subsequent REST calls to 
> server that access data/user metadata of the file will require fetching the 
> encryption context through a GetFileProperties call and retrieving the key 
> from the custom provider, before sending the request.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to