update mistake in change log and add ex. for create blob in directory (#46693)

* update mistake in change log and add example for blob client in directory

* change / to %2F

* add space

* add space

* add space

* update readmesamples and updated readme files

* remove comments from directory blob client creation

* add space

* copilot changed a readme in gh, but didn't change the samplesFile

* update blob-crypto and datalake changelogs with clearer example

Author: browndav-msft

sdk/storage/azure-storage-blob-cryptography/CHANGELOG.md

@@ -152,10 +152,10 @@
 
 ### Breaking Changes
 - When creating a `EncryptedBlobClient` via EncryptedBlobClientBuilder, the blob name will be stored exactly as passed 
-  in and will not be URL-encoded. For example, if blob name is "test%25test" and is created by calling
-  `EncryptedBlobClientBuilder.blobName("test%25test")` along with other required parameters, 
-  `EncryptedBlobClient.getBlobName()` will return "test%25test" and the blob's url will result in 
-  “https://account.blob.core.windows.net/container/test%25%25test”.
+  in and will not be URL-encoded. For example, if blob name is "directory/blob.txt" and is created by calling
+  `EncryptedBlobClientBuilder.blobName("directory/blob.txt")` along with other required parameters, 
+  `EncryptedBlobClient.getBlobName()` will return "directory/blob.txt" and the blob's url will result in 
+  “https://account.blob.core.windows.net/container/directory%2Fblob.txt”.
 
 ### Other Changes
 

sdk/storage/azure-storage-blob/CHANGELOG.md

@@ -231,10 +231,10 @@
 ### Breaking Changes
 - When creating a `BlobClient` via `BlobContainerClient.getBlobClient(String blobName)` or 
 `BlobServiceClient.getBlobClient(String blobName)`, the blob name will be stored exactly as passed in and will not be 
-URL-encoded. For example, if blob name is "test%25test" and is created by calling 
-`BlobContainerClient.getBlobClient("test%25test")` or `BlobClient.getBlobName("test%25test")`, 
-`BlobClient.getBlobName()` will return "test%25test" and the blob's url will result in 
-“https://account.blob.core.windows.net/container/test%25%25test”.
+URL-encoded. For example, if blob name is "directory/blob.txt" and is created by calling 
+`BlobContainerClient.getBlobClient("directory/blob.txt")`, 
+`BlobClient.getBlobName()` will return "directory/blob.txt" and the blob's url will result in 
+“https://account.blob.core.windows.net/container/directory%2Fblob.txt". 
 
 ## 12.25.3 (2024-03-20)
 

sdk/storage/azure-storage-blob/README.md

@@ -251,7 +251,7 @@ BlobClient blobClient = blobContainerClient.getBlobClient("myblob");
 
 or
 
-Create a `BlobClient` from the builder [`sasToken`](#get-credentials) generated above.
+Create a `BlobClient` within a directory structure using `BlobContainerClient`. 
 
 ```java readme-sample-getBlobClient2
 BlobClient blobClient = new BlobClientBuilder()
@@ -264,8 +264,27 @@ BlobClient blobClient = new BlobClientBuilder()
 
 or
 
+Create a `BlobClient` from the builder [`sasToken`](#get-credentials) generated above.
+
 ```java readme-sample-getBlobClient3
-// Only one "?" is needed here. If the SAS token starts with "?", please removing one "?".
+BlobClient blobClient = blobContainerClient.getBlobClient("directory/myblob");
+```
+
+or
+
+```java readme-sample-getBlobClient4
+BlobClient blobClient = new BlobClientBuilder()
+    .endpoint("<your-storage-account-url>")
+    .sasToken("<your-sasToken>")
+    .containerName("mycontainer")
+    .blobName("directory/myblob")
+    .buildClient();
+```
+
+or
+
+```java readme-sample-getBlobClient5
+// Only one "?" is needed here. If the SAS token starts with "?", please remove one "?".
 BlobClient blobClient = new BlobClientBuilder()
     .endpoint("<your-storage-account-url>" + "/" + "mycontainer" + "/" + "myblob" + "?" + "<your-sasToken>")
     .buildClient();

sdk/storage/azure-storage-blob/src/samples/java/com/azure/storage/blob/ReadmeSamples.java

@@ -106,11 +106,28 @@ public void getBlobClient2() {
 
     public void getBlobClient3() {
         // BEGIN: readme-sample-getBlobClient3
-        // Only one "?" is needed here. If the SAS token starts with "?", please removing one "?".
+        BlobClient blobClient = blobContainerClient.getBlobClient("directory/myblob");
+        // END: readme-sample-getBlobClient3
+    }
+
+    public void getBlobClient4() {
+        // BEGIN: readme-sample-getBlobClient4
+        BlobClient blobClient = new BlobClientBuilder()
+            .endpoint("<your-storage-account-url>")
+            .sasToken("<your-sasToken>")
+            .containerName("mycontainer")
+            .blobName("directory/myblob")
+            .buildClient();
+        // END: readme-sample-getBlobClient4
+    }
+
+    public void getBlobClient5() {
+        // BEGIN: readme-sample-getBlobClient5
+        // Only one "?" is needed here. If the SAS token starts with "?", please remove one "?".
         BlobClient blobClient = new BlobClientBuilder()
             .endpoint("<your-storage-account-url>" + "/" + "mycontainer" + "/" + "myblob" + "?" + "<your-sasToken>")
             .buildClient();
-        // END: readme-sample-getBlobClient3
+        // END: readme-sample-getBlobClient5
     }
 
     public void createBlobContainerClient1() {
@@ -379,4 +396,3 @@ public void setProxy2() {
         // END: readme-sample-setProxy2
     }
 }
-

sdk/storage/azure-storage-file-datalake/CHANGELOG.md

@@ -187,9 +187,9 @@
 - When creating a `DataLakeFileClient` or `DataLakeDirectoryClient` via `DataLakeFileSystemClient.getDirectoryClient(String directoryName)`,
   `DataLakeFileSystemClient.getDirectoryClient(String fileName)`, `DataLakeDirectoryClient.getSubDirectoryClient(String blobName)`
   and `DataLakeDirectoryClient.getSubDirectoryClient(String blobName)`, the path name will be stored exactly as passed in
-  and will not be URL-encoded. For example, if the path name is "test%25test" and is created by calling `DataLakeFileSystemClient.getDirectoryClient("test%25test")`,
-  `DataLakeDirectoryClient.getDirectoryPath()` will return "test%25test" and the path's url will result in
-  “https://account.dfs.core.windows.net/filesystemname/test%25%25test”.
+  and will not be URL-encoded. For example, if the path name is "directory/blob.txt" and is created by calling `DataLakeFileSystemClient.getDirectoryClient("directory/blob.txt")`,
+  `DataLakeDirectoryClient.getDirectoryPath()` will return "directory/blob.txt" and the path's url will result in
+  “https://account.dfs.core.windows.net/filesystemname/directory%2Fblob.txt”.
 
 ### Bugs Fixed
 - Fixed a bug that did not allow uploading an empty 0 byte file with `DataLakeFileClient.uploadFromFile()`.
@@ -222,9 +222,9 @@
 - When creating a `DataLakeFileClient` or `DataLakeDirectoryClient` via `DataLakeFileSystemClient.getDirectoryClient(String directoryName)`,
   `DataLakeFileSystemClient.getDirectoryClient(String fileName)`, `DataLakeDirectoryClient.getSubDirectoryClient(String blobName)` 
 and `DataLakeDirectoryClient.getSubDirectoryClient(String blobName)`, the path name will be stored exactly as passed in 
-and will not be URL-encoded. For example, if the path name is "test%25test" and is created by calling `DataLakeFileSystemClient.getDirectoryClient("test%25test")`,
-`DataLakeDirectoryClient.getDirectoryPath()` will return "test%25test" and the path's url will result in 
-“https://account.dfs.core.windows.net/filesystemname/test%25%25test”.
+and will not be URL-encoded. For example, if the path name is "directory/blob.txt" and is created by calling `DataLakeFileSystemClient.getDirectoryClient("directory/blob.txt")`,
+`DataLakeDirectoryClient.getDirectoryPath()` will return "directory/blob.txt" and the path's url will result in 
+“https://account.dfs.core.windows.net/filesystemname/directory%2Fblob.txt”.
 
 ### Bugs Fixed
 - Fixed a bug that did not allow uploading an empty 0 byte file with `DataLakeFileClient.uploadFromFile()`.