[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hadoop-dev
Subject:    [jira] [Created] (HADOOP-18580) Special characters handling in Azure file system is different from o
From:       "Yuya Ebihara (Jira)" <jira () apache ! org>
Date:       2022-12-16 12:56:00
Message-ID: JIRA.13514219.1671195351000.208575.1671195360008 () Atlassian ! JIRA
[Download RAW message or body]

Yuya Ebihara created HADOOP-18580:
-------------------------------------

             Summary: Special characters handling in Azure file system is different \
from others  Key: HADOOP-18580
                 URL: https://issues.apache.org/jira/browse/HADOOP-18580
             Project: Hadoop Common
          Issue Type: Bug
          Components: fs/azure
    Affects Versions: 3.2.0
            Reporter: Yuya Ebihara


Special character's handling in \
[AzureBlobFileSystem|[https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azurebfs/AzureBlobFileSystem.java]] \
looks different from other file systems. e.g.  GoogleHadoopFileSystem.

For instance, FileSystem.open with `.../part=a%25percent/test.parquet` works fine in \
other file systems, but ABFS requires `.../part=a%percent/test.parquet` (%25 → %) \
because the path is URL encoded by \
`org.apache.hadoop.fs.azurebfs.services.AbfsClient#createRequestUrl` internally. Can \
we change the behavior? Or can I request to add javadoc to explain the behavior if \
this is the expected behavior?  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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


[prev in list] [next in list] [prev in thread] [next in thread]