Update docs based on code PR #4

docs/api/openapi/openapi-usage-guide.md

@@ -363,6 +363,11 @@ Collection includes a POST, GET, and DELETE for a single entity with a SchemaMet
                   "value": "urn:li:dataset:(urn:li:dataPlatform:platform,testSchemaIngest,PROD)",
                   "description": "(Required) A list of raw urn strings, only supports a single entity type per request."
                 },
+                {
+                  "key": "filters",
+                  "value": "{\"and\": [{\"field\": \"resourceType\", \"condition\": \"EQUAL\", \"value\": \"test_resource_type\"}], \"or\": []}",
+                  "description": "Optional filters to apply to the query, supporting 'and' and 'or' conditions."
+                },
                 {
                   "key": "urns",
                   "value": "labore dolor exercitation in",

docs/api/restli/restli-overview.md

@@ -1140,7 +1140,7 @@ curl -X POST 'http://localhost:8080/entities?action=search' \
 
 ###### Filtering
 
-In addition to performing full-text search, you can also filter explicitly against fields marked as @Searchable in the corresponding aspect PDLs.
+In addition to performing full-text search, you can also filter explicitly against fields marked as @Searchable in the corresponding aspect PDLs. The filtering can be done using either AND or OR conditions, but not both simultaneously.
 
 For example, to perform filtering for a chart with title "Baz Chart 1", you could issue the following query:
 

docs/how/delete-metadata.md

@@ -31,7 +31,7 @@ All the commands below support the following options:
 
 ### Selecting entities to delete
 
-You can either provide a single urn to delete, or use filters to select a set of entities to delete.
+You can either provide a single urn to delete, or use filters to select a set of entities to delete. Filters can now be specified using AND/OR conditions for more flexible querying.
 
 ```shell
 # Soft delete a single urn.

docs/how/search.md

@@ -207,7 +207,7 @@ query searchEntities {
 
 ### Searching at Scale
 
-For queries that return more than 10k entities we recommend using the [scrollAcrossEntities](https://datahubproject.io/docs/graphql/queries/#scrollacrossentities) GraphQL API: 
+For queries that return more than 10k entities, or when using indexed queries with AND/OR filters, we recommend using the [scrollAcrossEntities](https://datahubproject.io/docs/graphql/queries/#scrollacrossentities) GraphQL API: 
 
 ```
 # Example query
@@ -267,7 +267,7 @@ In order to complete scrolling through all of the results, continue to request d
 
 ## Customizing Search
 
-It is possible to completely customize search ranking, filtering, and queries using a search configuration yaml file.
+The new `search_by_filters` method allows for indexed queries using AND/OR filters, enhancing search capabilities. Additionally, it is possible to completely customize search ranking, filtering, and queries using a search configuration yaml file.
 This no-code solution provides the ability to extend, or replace, the Elasticsearch-based search functionality. The
 only limitation is that the information used in the query/ranking/filtering must be present in the entities' document,
 however this does include `customProperties`, `tags`, `terms`, `domain`, as well as many additional fields.

docs/how/updating-datahub.md

@@ -272,6 +272,7 @@ New (optional fields `systemMetadata` and `headers`):
   Otherwise, we recommend soft deleting all databricks data via the DataHub CLI:
   `datahub delete --platform databricks --soft` and then reingesting with `include_metastore: false`.
 - #8846 - Changed enum values in resource filters used by policies. `RESOURCE_TYPE` became `TYPE` and `RESOURCE_URN` became `URN`.
+- Added support for indexed queries with URNs in platform resources, allowing the use of 'and' and 'or' filters. Ensure that only one type of filter is provided at a time to avoid errors.
   Any existing policies using these filters (i.e. defined for particular `urns` or `types` such as `dataset`) need to be upgraded
   manually, for example by retrieving their respective `dataHubPolicyInfo` aspect and changing part using filter i.e.