Written by The Jahia Team
 
Developers
   Estimated reading time:

For documents to be searchable, they need to be indexed in an Elasticsearch cluster first. This is done by identifying main resource nodes, along with their sub-nodes, as defined in Augmented Search configuration file.

As part of the indexing process, corresponding ACLs and roles (from the source nodes) are attached to the Elasticsearch documents. This allows Augmented Search to return search results matching a visitor's permissions.

Triggering indexing

Indexing is triggered by the following type of events:

  • Clicking on Index contents in the Augmented Search section in Jahia Administration. This triggers a full reindexing of the site.
  • Creating or modifying content on a site. This triggers indexing of the new or modified content (not the full site). The content becomes available for search almost immediately after publication.
  • Creating a site. This triggers indexing of the full site.
  • Importing content. This triggers indexing of the new or modified content. 

Indexing time depends on the number of documents to be indexed. For page updates, documents are available almost immediately. For large full-site indexing, expect indexing to take a couple of minutes.

Excluding a document

In some situations, it might be necessary to exclude a document from Augmented Search. For example, to ensure that specific content does not display in an excerpt (see Search results and content filtering).

You can exclude content by using the Remove From Augmented Search Results mixin. If the document was previously indexed, it will be removed from Augmented Search upon save. Excluding a parent will also exclude all of its subpages.

augmented-search-skip-index.png

Modifying mappings

Note that any modifications to the Elasticsearch mapping requires a reindexing of the content.