Skip to content

Commit 9aba9e7

Browse files
authored
Merge pull request #116550 from xyh1/patch-117
new regions
2 parents 1aa3697 + 872ec2a commit 9aba9e7

File tree

1 file changed

+15
-3
lines changed

1 file changed

+15
-3
lines changed

articles/storage/blobs/storage-manage-find-blobs.md

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ The following limits apply to Blob Index tags:
6666
- Tag keys must be between 1 to 128 characters
6767
- Tag values must be between 0 to 256 characters
6868
- Tag keys and values are case-sensitive
69-
- Tag keys and values only support string data types; any numbers or special characters will be saved as strings
69+
- Tag keys and values only support string data types; any numbers, date, times, or special characters will be saved as strings
7070
- Tag keys and values must adhere to the following naming rules:
7171
- Alpha numeric characters: a-z, A-Z, 0-9
7272
- Special characters: space, plus, minus, period, colon, equals, underscore, forward slash
@@ -103,6 +103,13 @@ The below table shows all the valid operators for FindBlobsByTags:
103103
| AND | Logical and | "Rank" >= '010' AND "Rank" < '100' |
104104
| @container | Scope to a specific container | @container = 'videofiles' AND "status" = 'done' |
105105

106+
> [!NOTE]
107+
> Be familiar with lexicographical ordering when setting and querying on tags.
108+
> - Numbers are sorted before letters. Numbers are sorted based on the first digit.
109+
> - Uppercase letters are sorted before lowercase letters.
110+
> - Symbols are not standard. Some symbols are sorted before numeric values. Other symbols are sorted before or after letters.
111+
>
112+
106113
## Conditional Blob operations with Blob Index tags
107114
In REST versions 2019-10-10 and higher, most [blob service APIs](https://docs.microsoft.com/rest/api/storageservices/operations-on-blobs) now support a conditional header, x-ms-if-tags, such that the operation will only succeed if the specified blob index condition is met. If the condition is not met, you will get `error 412: The condition specified using HTTP conditional header(s) is not met`.
108115

@@ -243,9 +250,11 @@ Blob Index pricing is currently in public preview and subject to change for gene
243250

244251
## Regional availability and storage account support
245252

246-
Blob Index is currently available with General Purpose v2 (GPv2) accounts only. In the Azure portal, you can upgrade an existing General Purpose (GPv1) account to a GPv2 account. For more information about storage accounts, see [Azure storage account overview](../common/storage-account-overview.md).
253+
Blob Index is currently only available on General Purpose v2 (GPv2) accounts with hierarchical namespace (HNS) disabled. General Purpose (GPV1) accounts are not supported but you can upgrade any GPv1 account to a GPv2 account. For more information about storage accounts, see [Azure storage account overview](../common/storage-account-overview.md).
247254

248255
In public preview, Blob Index is currently only available in the following select regions:
256+
- Canada Central
257+
- Canada East
249258
- France Central
250259
- France South
251260

@@ -273,7 +282,7 @@ az provider register --namespace 'Microsoft.Storage'
273282
This section describes known issues and conditions in the current public preview of the Blob Index. As with most previews, this feature should not be used for production workloads until it reaches GA as behaviors may change.
274283

275284
- For preview, you must first register your subscription before you can use Blob Index for your storage account in the preview regions.
276-
- Only GPv2 accounts are currently supported in preview. Blob, BlockBlobStorage, and HNS enabled DataLake Gen2 accounts are not currently supported with Blob Index.
285+
- Only GPv2 accounts are currently supported in preview. Blob, BlockBlobStorage, and HNS enabled DataLake Gen2 accounts are not currently supported with Blob Index. GPv1 accounts will not be supported.
277286
- Uploading page blobs with index tags currently does not persist the tags. You must set the tags after uploading a page blob.
278287
- When filtering is scoped to a single container, the @container can only be passed if all the index tags in the filter expression are equality checks (key=value).
279288
- When using the range operator with the AND condition, you can only specify the same index tag key name (Age > ‘013’ AND Age < ‘100’).
@@ -288,6 +297,9 @@ This section describes known issues and conditions in the current public preview
288297
### Can Blob Index help me filter and query content inside my blobs?
289298
No, Blob Index tags can help you find the blobs that you are looking for. If you need to search within your blobs, use Query Acceleration or Azure Search.
290299

300+
### Are there any special considerations regarding Blob Index tag values?
301+
Blob Index tags only support string data types and querying returns results with lexicographical ordering. For numbers, it is recommended to zero pad the number. For date and times, it is recommended to store as an ISO 8601 compliant format.
302+
291303
### Are Blob Index tags and Azure Resource Manager tags related?
292304
No, Azure Resource Manager tags help organize control plane resources such as subscriptions, resource groups, and storage accounts. Blob Index tags provide object management and discovery on data plane resources such as blobs within a storage account.
293305

0 commit comments

Comments
 (0)