[
https://issues.apache.org/jira/browse/HDFS-11286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sampada Dehankar updated HDFS-11286:
------------------------------------
Description:
We use ADLS to store customer data and to access the data from our containers
HttpFS Server-Client is used. HttpFS functions like GETFILESTATUS, RENAME
expect absolute 'path' of the file(s) as the argument. But when the request is
received at the server from HttpFs Client, the server is forwarding only the
relative path rather than absolute path to ADLS. This is breaking the logic for
GETFILESTATUS, RENAME functions.
Steps to reproduce GETFILESTATUS Command Bug:
Run the following command from the client:
Example 1:
hadoop fs –ls adl_scheme://account/folderA/folderB/
Server logs show only the relative path "folderA/folderB/" is forwarded to
ADLS.
Example 2:
hadoop fs –ls adl_scheme://account/folderX/folderY/SampleFile
Server logs show only the relative path "folderX/folderY/SampleFile" is
forwarded to ADLS.
Fix:
Prepend the ADLS scheme and account name to the path. So the path in example 1
and example 2 would look like this 'adl_scheme://account/folderA/folderB/' and
'adl_scheme://account/folderX/folderY/SampleFile' respectively.
Steps to reproduce RENAME Command Bug:
Run the following command from the client:
Example 1:
Hadoop fs –mv /folderA/oldFileName /folderA/newFileName
Server logs show only the relative old file path "folderA/oldFileName" and new
File path "adl_scheme://account/folderA/newFileName" is forwarded to ADLS.
Fix:
Prepend the ADLS scheme and account name to the old file name path.
was:
We use ADLS to store customer data and to access the data from our containers
HttpFS Server-Client is used. HttpFS functions like GETFILESTATUS, RENAME
expect absolute 'path' of the file(s) as the argument. But when the request is
received at the server from HttpFs Client, the server is forwarding only the
relative path rather than absolute path to ADLS. This is breaking the logic for
GETFILESTATUS, RENAME functions.
Steps to reproduce GETFILESTATUS Command Bug:
Run the following command from the client:
Example 1:
hadoop fs –ls adl_scheme://account/folderA/folderB/
Server logs show only the relative path "folderA/folderB/" is forwarded to
ADLS.
Example 2:
hadoop fs –ls adl_scheme://account/folderX/folderY/SampleFile
Server logs show only the relative path "folderX/folderY/SampleFile" is
forwarded to ADLS.
Fix:
Prepend the ADLS scheme and account name to the path. So the path in example 1
and example 2 would look like this 'adl_scheme://account/folderA/folderB/' and
'adl_scheme://account/folderX/folderY/SampleFile' respectively. We have the fix
ready and currently it is in the testing phase.
Steps to reproduce RENAME Command Bug:
Run the following command from the client:
Example 1:
Hadoop fs –mv /folderA/oldFileName /folderA/newFileName
Server logs show only the relative old file path "folderA/oldFileName" and new
File path "adl_scheme://account/folderA/newFileName" is forwarded to ADLS.
Fix:
Prepend the ADLS scheme and account name to the old file name path. We have the
fix ready and currently it is in the testing phase.
> GETFILESTATUS, RENAME logic breaking due to incomplete path argument
> ---------------------------------------------------------------------
>
> Key: HDFS-11286
> URL: https://issues.apache.org/jira/browse/HDFS-11286
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: httpfs
> Affects Versions: 2.7.1
> Environment: Windows
> Reporter: Sampada Dehankar
> Labels: bugfix, patch
>
> We use ADLS to store customer data and to access the data from our containers
> HttpFS Server-Client is used. HttpFS functions like GETFILESTATUS, RENAME
> expect absolute 'path' of the file(s) as the argument. But when the request
> is received at the server from HttpFs Client, the server is forwarding only
> the relative path rather than absolute path to ADLS. This is breaking the
> logic for GETFILESTATUS, RENAME functions.
>
> Steps to reproduce GETFILESTATUS Command Bug:
>
> Run the following command from the client:
>
> Example 1:
> hadoop fs –ls adl_scheme://account/folderA/folderB/
> Server logs show only the relative path "folderA/folderB/" is forwarded to
> ADLS.
>
> Example 2:
> hadoop fs –ls adl_scheme://account/folderX/folderY/SampleFile
> Server logs show only the relative path "folderX/folderY/SampleFile" is
> forwarded to ADLS.
>
> Fix:
> Prepend the ADLS scheme and account name to the path. So the path in example
> 1 and example 2 would look like this 'adl_scheme://account/folderA/folderB/'
> and 'adl_scheme://account/folderX/folderY/SampleFile' respectively.
>
> Steps to reproduce RENAME Command Bug:
>
> Run the following command from the client:
>
> Example 1:
> Hadoop fs –mv /folderA/oldFileName /folderA/newFileName
>
> Server logs show only the relative old file path "folderA/oldFileName" and
> new File path "adl_scheme://account/folderA/newFileName" is forwarded to
> ADLS.
>
> Fix:
>
> Prepend the ADLS scheme and account name to the old file name path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
