Skip to content

Commit 730ccb5

Browse files
rephrasing in terms of Lucene docs
1 parent 5ce18f9 commit 730ccb5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/search/search-limits-quotas-capacity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ To determine whether your service has document limits, check the Usage tile in t
6262

6363
![Usage tile](media/search-limits-quotas-capacity/portal-usage-tile.png)
6464

65-
<sup>1</sup> Even though there aren't any SKU specific document limits, every index is still subject to a maximum safe limit to ensure stability of the service. The number of documents is bound by an underlying lucene limit. It's hard to precisely determine the limit as it depends on factors like number of complex collections and number of internal sub-indexes modeling the original index. For indexes without any complex collections, it is roughly around 25 billion. Using complex collections can significantly lower this limit.
65+
<sup>1</sup> Even though there aren't any SKU specific document limits, every index is still subject to a maximum safe limit to ensure stability of the service. This limit comes from Lucene. Every Azure Search document is internally indexed as one or more Lucene documents. The number of Lucene documents per Azure search document depends on the total number of elements in complex collection fields. Each element is indexed as a separate Lucene document. For example, a document with 3 elements in a complex collection field, will be indexed as 4 Lucene documents - 1 for the document itself and 3 for the elements. The maximum number of Lucene documents that can be indexed is roughly 25 billion which is the upper bound for the number of documents in an Azure search index.
6666

6767
### Regions previously having document limits
6868

0 commit comments

Comments
 (0)