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

ASF GitHub Bot logged work on HADOOP-17912:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/May/22 11:33
            Start Date: 13/May/22 11:33
    Worklog Time Spent: 10m 
      Work Description: sumangala-patki commented on PR #3440:
URL: https://github.com/apache/hadoop/pull/3440#issuecomment-1125963275

   Failures above are tracked in JIRAs/observed on trunk




Issue Time Tracking
-------------------

    Worklog Id:     (was: 770134)
    Time Spent: 40m  (was: 0.5h)

> 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
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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.20.7#820007)

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

Reply via email to