Unable to create a directory named space character using ADLS Gen2 REST API

Hi Phil R ,

Given that the Hadoop ABFS HCFS driver is Azure-supplied and supported, and that it handles encoding internally, it seems the issue is specific to how ADLS Gen2 handles directory names with space characters, ensure that there are no specific constraints or limitations mentioned regarding directory names with space characters. The Path - Create REST API documentation might provide some insights

The Known Issues and Feature Support for ADLS Gen2 might have relevant information

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.

Hi Phil R ,

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.

Hi Phil R ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet .In case if you have any resolution please do share that same with the community as it can be helpful to others . Otherwise, will respond back with the more details and we will try to help.

I have looked at the REST API documentation you have listed. It would fall under the "path" parameter, which is listed as type string and is required. It does not list any validation other validation requirements. For example, the "filesystem" parameter lists a regular expression that the input must match. There is nothing for "path", or other wording at all throughout that implies any value that is or is not supported. As it is a required string, this suggests "subdira/ " (space following slash) would be a valid value, as is satisfies the string type and required element.

As was noted in the original post, I highlighted that we had already reviewed both the feature support and known issued, and it does not list that a space character would be prohibited.

I additionally noted that per the feature support, it directly states it is built on "blob storage" https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-introduction#built-on-azure-blob-storage

To quote the specific support

Because these capabilities are built on Blob Storage, features such as diagnostic logging, access tiers, and lifecycle management policies are available to your account. Most Blob Storage features are fully supported, but some features might be supported only at the preview level and there are a handful of them that aren't yet supported. For a complete list of support statements, see Blob Storage feature support in Azure Storage accounts. The status of each listed feature will change over time as support continues to expand.

The very implication of this statement implies that the functionality it supports should be consulted from the blob storage documentation, and enhanced by the ADLS Gen2 documentation.

Blog storage documentation expressly states in https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction#blobs

Follow these rules when naming a blob:

• A blob name can contain any combination of characters.
• A blob name must be at least one character long and cannot be more than 1,024 characters long, for blobs in Azure Storage.
• Blob names are case-sensitive.
• Reserved URL characters must be properly escaped.
• There are limitations on the number of path segments comprising a blob name. A path segment is the string between consecutive delimiter characters (for example, a forward slash /) that corresponds to the directory or virtual directory. The following path segment limitations apply to blob names:
  • If the storage account does not have hierarchical namespace enabled, the number of path segments comprising the blob name cannot exceed 254.
  • If the storage account has hierarchical namespace enabled, the number of path segments comprising the blob name cannot exceed 63 (including path segments for container name and account host name).

Per this, a space character is expressly permitted, provided it is escaped. A space counts as the "at least one character" and it doesn't fall found of the path segment limitations.

And as ADLS Gen2 "enhances" the blob storage docs, and said enhancements do no mention this further, this implies there are no rules that change the above rules either to degrade or elevate the capabilities.

For all intent and purposes, it implies it is supported.

So why does it not function?

I'm not after a back and forward on the documentation, as I have extensively read it and even quoted relevant portions that would lead one to conclude this is a supported scenario. I am after technical confirmation that confirms it is not supported and thus, appropriate documentation updates to reflect it - or better, a fix that makes it function as the documentation implies it should.

There are really only two possible conclusions that should be occurring here, a docs update, or a fix. Instead we are on a merry go round of "Please see this page that says nothing about the answer you are looking for". I came for answers, not homework.