Merge pull request #78272 from brjohnstmsft/search-filters

[Azure Search] Rewriting OData language reference

Author: rjagiewich

articles/search/TOC.yml

@@ -233,16 +233,18 @@
       href: search-query-lucene-examples.md
     - name: moreLikeThis (preview)
       href: search-more-like-this.md
-  - name: Filter and sort data
+  - name: Use filters
     items:
     - name: Filter overview
       href: search-filters.md
     - name: Facet filters
       href: search-filters-facets.md
     - name: Add faceted navigation
       href: search-faceted-navigation.md
-    - name: Filter and OrderBy expression syntax and examples
-      href: query-odata-filter-orderby-syntax.md
+    - name: Troubleshoot collection filters
+      href: search-query-troubleshoot-collection-filters.md
+    - name: Understand collection filters
+      href: search-query-understand-collection-filters.md
   - name: Handle results
     items:
     - name: Page-related features
@@ -283,6 +285,32 @@
     href: search-api-preview.md
   - name: Resource Manager template
     href: /azure/templates/microsoft.search/searchservices
+  - name: OData language reference
+    items:
+    - name: Overview
+      href: query-odata-filter-orderby-syntax.md
+    - name: $filter
+      href: search-query-odata-filter.md
+    - name: $orderby
+      href: search-query-odata-orderby.md
+    - name: $select
+      href: search-query-odata-select.md
+    - name: any, all
+      href: search-query-odata-collection-operators.md
+    - name: eq, ne, gt, lt, ge, le
+      href: search-query-odata-comparison-operators.md
+    - name: search.ismatch, search.ismatchscoring
+      href: search-query-odata-full-text-search-functions.md
+    - name: geo.distance, geo.intersects
+      href: search-query-odata-geo-spatial-functions.md
+    - name: and, or, not
+      href: search-query-odata-logical-operators.md
+    - name: search.in
+      href: search-query-odata-search-in-function.md
+    - name: search.score
+      href: search-query-odata-search-score-function.md
+    - name: OData Language Grammar
+      href: search-query-odata-syntax-reference.md
   - name: Cognitive skills reference
     href: cognitive-search-predefined-skills.md
     items:

articles/search/query-odata-filter-orderby-syntax.md

@@ -6,7 +6,7 @@ manager: cgronlun
 services: search
 ms.service: search
 ms.topic: conceptual
-ms.date: 05/13/2019
+ms.date: 06/13/2019
 ms.author: heidist
 ms.custom: seodec2018
 ---
@@ -152,11 +152,11 @@ Text strings are case-sensitive. There is no lower-casing of upper-cased words:
 
 ### Approaches for filtering on text
 
-| Approach | Description | When to use | 
+| Approach | Description | When to use |
 |----------|-------------|-------------|
-| [search.in](query-odata-filter-orderby-syntax.md) | A function that matches a field against a delimited list of strings. | Recommended for [security filters](search-security-trimming-for-azure-search.md) and for any filters where many raw text values need to be matched with a string field. The **search.in** function is designed for speed and is much faster than explicitly comparing the field against each string using `eq` and `or`. | 
-| [search.ismatch](query-odata-filter-orderby-syntax.md) | A function that allows you to mix full-text search operations with strictly Boolean filter operations in the same filter expression. | Use **search.ismatch** (or its scoring equivalent, **search.ismatchscoring**) when you want multiple search-filter combinations in one request. You can also use it for a *contains* filter to filter on a partial string within a larger string. |
-| [$filter=field operator string](query-odata-filter-orderby-syntax.md) | A user-defined expression composed of fields, operators, and values. | Use this when you want to find exact matches between a string field and a string value. |
+| [`search.in`](search-query-odata-search-in-function.md) | A function that matches a field against a delimited list of strings. | Recommended for [security filters](search-security-trimming-for-azure-search.md) and for any filters where many raw text values need to be matched with a string field. The **search.in** function is designed for speed and is much faster than explicitly comparing the field against each string using `eq` and `or`. | 
+| [`search.ismatch`](search-query-odata-full-text-search-functions.md) | A function that allows you to mix full-text search operations with strictly Boolean filter operations in the same filter expression. | Use **search.ismatch** (or its scoring equivalent, **search.ismatchscoring**) when you want multiple search-filter combinations in one request. You can also use it for a *contains* filter to filter on a partial string within a larger string. |
+| [`$filter=field operator string`](search-query-odata-comparison-operators.md) | A user-defined expression composed of fields, operators, and values. | Use this when you want to find exact matches between a string field and a string value. |
 
 ## Numeric filter fundamentals