You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/purview/how-to-resource-set-pattern-rules.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,14 +6,14 @@ ms.author: nayenama
6
6
ms.service: purview
7
7
ms.subservice: purview-data-map
8
8
ms.topic: how-to
9
-
ms.date: 09/27/2021
9
+
ms.date: 12/06/2022
10
10
---
11
11
12
12
# Create resource set pattern rules
13
13
14
14
At-scale data processing systems typically store a single table in storage as multiple files. This concept is represented in Microsoft Purview by using resource sets. A resource set is a single object in the data catalog that represents a large number of assets in storage. To learn more, see [Understanding resource sets](concept-resource-sets.md).
15
15
16
-
When scanning a storage account, Microsoft Purview uses a set of defined patterns to determine if a group of assets is a resource set. In some cases, Microsoft Purview's resource set grouping may not accurately reflect your data estate. Resource set pattern rules allow you to customize or override how Microsoft Purview detects which assets are grouped as resource sets and how they are displayed within the catalog.
16
+
When scanning a storage account, Microsoft Purview uses a set of defined patterns to determine if a group of assets is a resource set. In some cases, Microsoft Purview's resource set grouping may not accurately reflect your data estate. Resource set pattern rules allow you to customize or override how Microsoft Purview detects which assets are grouped as resource sets and how they're displayed within the catalog.
17
17
18
18
Pattern rules are currently supported in the following source types:
19
19
- Azure Data Lake Storage Gen2
@@ -66,7 +66,7 @@ For example, If two assets `folder1/file-1.csv` and `folder2/file-2.csv` matched
66
66
67
67
#### Special case: Dynamic replacers when not grouping into resource set
68
68
69
-
If *Do not group as resource set* is enabled for a pattern rule, the replacer name is an optional field. `{:<replacerType>}` is valid syntax. For example, `file-{:int}.csv` would successfully match for `file-1.csv` and `file-2.csv` and create two different assets instead of a resource set.
69
+
If *Don't group as resource set* is enabled for a pattern rule, the replacer name is an optional field. `{:<replacerType>}` is valid syntax. For example, `file-{:int}.csv` would successfully match for `file-1.csv` and `file-2.csv` and create two different assets instead of a resource set.
70
70
71
71
### Static replacers (double brackets)
72
72
@@ -82,15 +82,15 @@ Below are the available types that can be used in static and dynamic replacers:
82
82
83
83
| Type | Structure |
84
84
| ---- | --------- |
85
-
| string | A series of 1 or more Unicode characters including delimiters like spaces. |
86
-
| int | A series of 1 or more 0-9 ASCII characters, it can be 0 prefixed (e.g. 0001). |
85
+
| string | A series of one or more Unicode characters including delimiters like spaces. |
86
+
| int | A series of 1 or more 0-9 ASCII characters, it can be 0 prefixed (for example, 0001). |
87
87
| guid | A series of 32 or 8-4-4-4-12 string representation of an UUID as defined in [RFC 4122](https://tools.ietf.org/html/rfc4122). |
88
88
| date | A series of 6 or 8 0-9 ASCII characters with optionally separators: yyyymmdd, yyyy-mm-dd, yymmdd, yy-mm-dd, specified in [RFC 3339](https://tools.ietf.org/html/rfc3339). |
89
89
| time | A series of 4 or 6 0-9 ASCII characters with optionally separators: HHmm, HH:mm, HHmmss, HH:mm:ss specified in [RFC 3339](https://tools.ietf.org/html/rfc3339). |
90
90
| timestamp | A series of 12 or 14 0-9 ASCII characters with optionally separators: yyyy-mm-ddTHH:mm, yyyymmddhhmm, yyyy-mm-ddTHH:mm:ss, yyyymmddHHmmss specified in [RFC 3339](https://tools.ietf.org/html/rfc3339). |
91
91
| boolean | Can contain 'true' or 'false', case insensitive. |
92
-
| number | A series of 0 or more 0-9 ASCII characters, it can be 0 prefixed (e.g. 0001) followed by optionally a dot '.' and a series of 1 or more 0-9 ASCII characters, it can be 0 postfixed (e.g. .100) |
93
-
| hex | A series of 1 or more ASCII characters from the set 0-1 and A-F, the value can be 0 prefixed |
92
+
| number | A series of 0 or more 0-9 ASCII characters, it can be 0 prefixed (for example, 0001) followed by optionally a dot '.' and a series of 1 or more 0-9 ASCII characters, it can be 0 postfixed (for example, .100) |
93
+
| hex | A series of one or more ASCII characters from the set 0-1 and A-F, the value can be 0 prefixed |
94
94
| locale | A string that matches the syntax specified in [RFC 5646](https://tools.ietf.org/html/rfc5646). |
95
95
96
96
## Order of resource set pattern rules getting applied
0 commit comments