[Azure Search] Remove some service limits that aren't in the 2017-11-…

…11 API (Azure#2878)
KarishmaGhiya · Apr 18, 2018 · 4bd916d · 4bd916d
1 parent 9666a76
commit 4bd916d
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 15 deletions.
diff --git a/...t.Azure.Search.Service/preview/2017-11-11/examples/SearchServiceGetServiceStatistics.json b/...t.Azure.Search.Service/preview/2017-11-11/examples/SearchServiceGetServiceStatistics.json
@@ -34,9 +34,7 @@
                     }
                 },
                 "limits": {
-                    "maxFieldsPerIndex": 1000,
-                    "maxFieldNestingDepthPerIndex": 10,
-                    "maxComplexCollectionFieldsPerIndex": 100
+                    "maxFieldsPerIndex": 1000
                 }
             }
         }

diff --git a/...on/search/data-plane/Microsoft.Azure.Search.Service/preview/2017-11-11/searchservice.json b/...on/search/data-plane/Microsoft.Azure.Search.Service/preview/2017-11-11/searchservice.json
@@ -4065,18 +4065,6 @@
           "format": "int32",
           "x-nullable": true,
           "description": "The maximum allowed fields per index."
-        },
-        "maxFieldNestingDepthPerIndex": {
-          "type": "integer",
-          "format": "int32",
-          "x-nullable": true,
-          "description": "The maximum depth which you can nest sub-fields in an index, including the top-level complex field. For example, a/b/c has a nesting depth of 3."
-        },
-        "maxComplexCollectionFieldsPerIndex": {
-          "type": "integer",
-          "format": "int32",
-          "x-nullable": true,
-          "description": "The maximum number of fields of type Collection(Edm.ComplexType) allowed in an index."
         }
       },
       "description": "Represents various service level limits."