Skip to content

Commit 0f385c5

Browse files
committed
Some final tweaks
1 parent ac8a490 commit 0f385c5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/storage/blobs/upgrade-to-data-lake-storage-gen2-how-to.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Shows you how to use Resource Manager templates to upgrade from Azu
44
author: normesta
55
ms.service: storage
66
ms.topic: conceptual
7-
ms.date: 09/22/2022
7+
ms.date: 09/23/2022
88
ms.author: normesta
99

1010
---
@@ -26,7 +26,7 @@ To learn more about these capabilities and evaluate the impact of this upgrade o
2626

2727
2. Ensure that the segments of each blob path are named
2828

29-
The migration process creates a directory for each path segment of a blob. Data Lake Storage Gen2 directories must have a name, so for migration to succeed, each path segment in a virtual directory must have a name. The same requirement is true for segments that are named only with a space character. If any path segments are either unnamed (`//`) or named only with a space character (`_`), then you must copy those blobs to a new path that is compatible with these naming requirements. Then, you can proceed with the migration.
29+
The migration process creates a directory for each path segment of a blob. Data Lake Storage Gen2 directories must have a name so for migration to succeed, each path segment in a virtual directory must have a name. The same requirement is true for segments that are named only with a space character. If any path segments are either unnamed (`//`) or named only with a space character (`_`), then before you proceed with the migration, you must copy those blobs to a new path that is compatible with these naming requirements.
3030

3131
## Perform the upgrade
3232

0 commit comments

Comments
 (0)