hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HADOOP-17536) Suport for customer provided encrption key
Date Mon, 05 Apr 2021 07:54:00 GMT

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

ASF GitHub Bot logged work on HADOOP-17536:

                Author: ASF GitHub Bot
            Created on: 05/Apr/21 07:53
            Start Date: 05/Apr/21 07:53
    Worklog Time Spent: 10m 
      Work Description: snvijaya commented on a change in pull request #2707:
URL: https://github.com/apache/hadoop/pull/2707#discussion_r606969463

File path: hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azurebfs/services/AbfsHttpOperation.java
@@ -339,9 +340,10 @@ public void processResponse(final byte[] buffer, final int offset, final
int len
     if (this.requestId == null) {
       this.requestId = AbfsHttpConstants.EMPTY_STRING;
+    responseHeaders = AbfsIoUtils.getResponseHeaders(connection);
     // dump the headers
     AbfsIoUtils.dumpHeadersToDebugLog("Response Headers",
-        connection.getHeaderFields());
+        responseHeaders);

Review comment:
       Why is this change required ?

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 576729)
    Time Spent: 4h 40m  (was: 4.5h)

> Suport for customer provided encrption key
> ------------------------------------------
>                 Key: HADOOP-17536
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17536
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 3.4.0
>            Reporter: Bilahari T H
>            Assignee: Bilahari T H
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
> The data for a particular customer needs to be encrypted on account level. At server
side the APIs will start accepting the encryption key as part of request headers. The data
will be encrypted/decrypted with the given key at the server. 
> Since the ABFS FileSystem APIs are implementations for Hadoop FileSystem APIs there
is no direct way with which customer can pass the key to ABFS driver. In this case driver
should have the following capabilities so that it can accept and pass the encryption key as
one of the request headers. 
>  # There should be a way to configure the encryption key for different accounts.
>  # If there is a key specified for a particular account, the same needs to be sent along
with the request headers. 
> *Config changes* 
> They key for an account can be specified in the core-site as follows. 
> fs.azure.account.client-provided-encryption-key.{account name}.dfs.core.windows.net 

This message was sent by Atlassian Jira

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message