[jira] [Commented] (HADOOP-18580) Special characters handling in Azure file system is different from others
[ https://issues.apache.org/jira/browse/HADOOP-18580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727787#comment-17727787 ] Pranav Saxena commented on HADOOP-18580: AbfsClient#createRequestUrl uses URLEncoder.encode(val, UTF_8). {code:java} String val = ".../part=a%25percent/test.parquet"; System.out.println(URLEncoder.encode(val, UTF_8)); {code} gives: `...%2Fpart%3Da%2525percent%2Ftest.parquet` we can do something like: {code:java} URLEncoder.encode(val, UTF_8).replace("%2525", "%25") {code} > 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 >Priority: Minor > > Special characters 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 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-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18580) Special characters handling in Azure file system is different from others
[ https://issues.apache.org/jira/browse/HADOOP-18580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17686721#comment-17686721 ] Steve Loughran commented on HADOOP-18580: - so there's some double encoding going on? sounds like a bug note that azure doesn't like files ending with "."; everything gets to have its own quirk > 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 >Priority: Minor > > Special characters 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 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-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org