Error in Enabling Hierarchical Namespace for Azure Storage Account

Question

What should I do if I encounter a validation error while upgrading my Azure Blob Storage to Azure Data Lake Storage due to an invalid blob name containing a trailing slash?

 "PS - Based on common issues that we have seen from customers and other sources, we are posting these questions to help the Azure community."

Answer 1

Greetings!

If you encounter a validation error while upgrading your Azure Blob Storage to Azure Data Lake Storage (ADLS) due to an invalid blob name containing a trailing slash, follow these steps to resolve the issue:

1. Identify the Problem: The error occurs because the blob name contains a trailing slash, which is not permitted. This prevents the validation step from completing successfully.
2. Locate the Blob: Find the blob with the invalid name in your storage account. For example, the blob might be located in the container named chm-scrub-files.
3. Copy the Data: Copy the data from the problematic blob to a new blob without a trailing slash in its name.
4. Delete the Invalid Blob: Delete the original blob with the invalid name.
5. Retry the Upgrade: After deleting the problematic blob, retry the migration. The validation steps should now complete successfully.

It's crucial to ensure that all blob names adhere to the naming conventions to avoid such issues.Be cautious when deleting blobs to ensure no data is lost unintentionally. For further guidance on enabling the hierarchical namespace, refer to the following resources:

Resources:

• Upgrade Azure Blob Storage with Azure Data Lake Storage capabilities
• Upgrading Azure Blob Storage to Azure Data Lake Storage

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

Please do not forget to "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.