Merge pull request #197530 from djpmsft/purview-updates

Removing Search limitation

Author: PRMerger12

articles/purview/concept-resource-sets.md

@@ -6,7 +6,7 @@ ms.author: daperlov
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: conceptual
-ms.date: 09/24/2021
+ms.date: 05/09/2022
 ---
 
 # Understanding resource sets
@@ -45,21 +45,18 @@ When Microsoft Purview detects resources that it thinks are part of a resource s
 
 ## Advanced resource sets
 
-By default, Microsoft Purview determines the schema and classifications for resource sets based upon the [resource set file sampling rules](sources-and-scans.md#resource-set-file-sampling). Microsoft Purview can customize and further enrich your resource set assets through the **Advanced Resource Sets** capability. When Advanced Resource Sets are enabled, Microsoft Purview run extra aggregations to compute the following information about resource set assets:
+Microsoft Purview can customize and further enrich your resource set assets through the **Advanced Resource Sets** capability. Advanced resource sets allows Microsoft Purview to understand the underlying partitions of data ingested and enables the creation of [resource set pattern rules](how-to-resource-set-pattern-rules.md) that customize how Microsoft Purview groups resource sets during scanning. 
+ 
+When Advanced Resource Sets are enabled, Microsoft Purview run extra aggregations to compute the following information about resource set assets:
 
-- Most up-to-date schema and classifications to accurately reflect schema drift from changing metadata.
 - A sample path from a file that comprises the resource set.
 - A partition count that shows how many files make up the resource set. 
-- A schema count that shows how many unique schemas were found. This value is either a number between 1–5, or for values greater than 5, 5+.
-- A list of partition types when more than a single partition type is included in the resource set. For example, an IoT sensor might output both XML and JSON files, although both are logically part of the same resource set.
 - The total size of all files that comprise the resource set. 
 
 These properties can be found on the asset details page of the resource set.
 
 :::image type="content" source="media/concept-resource-sets/resource-set-properties.png" alt-text="The properties computed when advanced resource sets is on" border="true":::
 
-Enabling advanced resource sets also allows for the creation of [resource set pattern rules](how-to-resource-set-pattern-rules.md) that customize how Microsoft Purview groups resource sets during scanning. 
-
 ### Turning on advanced resource sets
 
 Advanced resource sets is off by default in all new Microsoft Purview instances. Advanced resource sets can be enabled from **Account information** in the management hub.
@@ -124,6 +121,11 @@ When scanning a storage account, Microsoft Purview uses a set of defined pattern
 
 To customize or override how Microsoft Purview detects which assets are grouped as resource sets and how they are displayed within the catalog, you can define pattern rules in the management center. For step-by-step instructions and syntax, please see [resource set pattern rules](how-to-resource-set-pattern-rules.md).
 
+## Known limitations with resource sets
+
+- By default, resource set assets will only be deleted by a scan if [Advanced Resource sets](#advanced-resource-sets) are enabled. If this capability is off, resource set assets can only be deleted manually or via API.
+- Currently, resource set assets will apply the first schema and classification discovered by the scan. Subsequent scans won't update the schema. 
+
 ## Next steps
 
 To get started with Microsoft Purview, see [Quickstart: Create a Microsoft Purview account](create-catalog-portal.md).

articles/purview/how-to-search-catalog.md

@@ -83,7 +83,6 @@ The following table contains the operators that can be used to compose a search
 
 ### Known limitations
 
-* Searching for classifications only matches on the formal classification name. For example, the keywords "World Cities" don't match classification "MICROSOFT.GOVERNMENT.CITY_NAME".
 * Grouping isn't supported within a field search. Customers should use operators to connect field searches. For example,`name:(alice AND bob)` is invalid search syntax, but `name:alice AND name:bob` is supported.
 
 ## Next steps