ContentSearchMaxScannedDocuments - System Parameter
New 7.12
ContentSearchMaxScannedDocuments is an integer System Parameter that limits how many documents Content Search reads in two cases: a Regular expression search, and the part of a Words or Phrase search that looks for a word hidden by formatting or a character entity. Content Search is the Search content dialog for Articles, Snippets, Templates, and Document Profiles. The Web API reads it for every such search.
At a Glance
| Property | Value |
|---|---|
| Key | ContentSearchMaxScannedDocuments |
| Data type | integer (the newest documents a search reads) |
| Default | 2000 |
| Read by | Web API |
| Takes effect | At the next search when saved on the System Parameters page; within about 15 seconds in other processes, such as the MCP Endpoint; no restart needed |
| Status | ✅ Active |
| Since | Nodinite 7.12 |
How It Works
- Words and Phrase searches narrow the documents in the database first. A regular expression can't be narrowed that way, so the search reads the newest ContentSearchMaxScannedDocuments documents and matches the expression against them.
- A word the reader sees can be hidden in the stored text: split by formatting (Order in bold followed by Number) or written with a character entity (
München). Words and Phrase searches look for such words in the newest ContentSearchMaxScannedDocuments documents only. Documents that hold the word as written are found in all documents, as before. - When a regular-expression search left documents out, the line above the results says only the newest N documents were searched. When only the look for hidden words was cut, no message is shown.
- Every regular expression still has a one-second time limit; a slower expression is stopped, whatever this value.
See Content Search - Limits for all three limits together.
Filter on ContentSearch to see the three Content Search limits together; this page covers ContentSearchMaxScannedDocuments.
Choosing a Value
Keep the default. When a regular-expression search reports that only the newest documents were searched, try Words or Phrase first: they search every document for the word as written. Raise the value when your Repository has more documents than the limit and you rely on regular expressions; each such search then reads more documents and takes longer.