How Does It Work?
The build group is responsible for:
-
Pushing and analyzing documents.
-
Creating the source index from which all the index replicas in your deployment are based.
Each build group contains:
- An indexing server, responsible for pushing and analyzing documents, and then importing the information into the next generation of the index.
- A specific configuration for the data model that defines the document processing and mapping done during analysis.
- A specific configuration for indexing that defines:
- How many analyzers (threads) to use for analysis.
- How often to compact the index.
- The conditions to trigger a commit of documents on disk to the index.
-
An index.
Note:
When the indexing server makes a commit, all build group components (DIH, thumbnails,
document cache, connector checkpoints, index inverted lists, and index dictionaries) are
saved to disk atomically.
By default, Exalead CloudView installs with:
-
A default build group,
bg0. -
A default data model,
default_model. -
A default indexing configuration,
ic0_standard.