arrow-down
    1. Overview
    2. Core concepts
    3. Using docs
    4. Intro Videos
    5. Tutorials
    1. Intro
    2. GraphQL API
    3. Media API
    4. Extending the API
    5. Component API
    1. Content Studio
      1. Branches
    2. Layers
      1. Lifecycle
      2. Media
      3. Attachments
      4. X-data
        1. Page templates
        2. Fragments
      5. Variants
      6. Permissions
      7. Versions
    3. Sites
      1. Visual editor
    4. Publishing
    1. Introduction
      1. Controllers
      2. Globals
      3. Events
      4. HTTP Request
      5. HTTP Response
      6. Error handler
      7. Filters
      8. Templating
      9. Localization
      10. Websocket
      11. Tasks
      12. Main controller
      13. Java bridge
      1. Admin Lib
      2. Application Lib
      3. Auditlog Lib
      4. Authentication Lib
      5. Cluster Lib
      6. Common Lib
      7. Content Lib
      8. Context Lib
      9. Event Lib
      10. Export Lib
      11. Grid Lib
      12. I18N Lib
      13. IO Lib
      14. Mail Lib
      15. Node Lib
      16. Portal Lib
      17. Project Lib
      18. Repo Lib
      19. Scheduler Lib
      20. Schema Lib
      21. Tasks Lib
      22. Value Lib
      23. VHost Lib
      24. Websocket Lib
    2. Other Libraries
      1. CLI
      2. Sandboxes
      3. Code
      4. Building
      5. Configuration
      6. TypeScript
    3. Building APIs
      1. Mappings
      2. Components
      3. Processors
      4. Contributions
    4. Building Webapps
      1. ID providers
      2. Admin Apps
      3. Admin Widgets
    1. Architecture
      1. TODO
      1. Navigating
      2. Users
      3. Applications
      4. Data management
      5. System info
      6. Audit Logs
      7. Task management
      1. Portal
      2. IDprovider
      3. Management
      4. Statistics
      1. Nodes and repos
      2. Properties
      3. Indexing
      4. Branches
      5. Editors
      1. DSL Queries
      2. NoQL Queries
      3. Filters
      4. Aggregations
      5. Highlighting
      1. ID providers
      2. System ID provider
      3. Users and groups
      4. Roles
      1. Strategies
      2. Distributions
      3. Docker
      4. Kubernetes
      5. Systemd
      6. Vhosts
      7. Configuration
      8. Backup & restore
      9. Clustering
      10. Observability
      1. Notes
      2. Upgrade
      3. Upgrading Apps
        1. Asset service
        2. HTTP service
        3. Image service
    1. Best practice
        1. AttachmentUploader
        2. Checkbox
        3. Combobox
        4. ContentSelector
        5. ContentTypeFilter
        6. CustomSelector
        7. Date
        8. DateTime
        9. Double
        10. GeoPoint
        11. HtmlArea
        12. ImageSelector
        13. Long
        14. MediaSelector
        15. Radiobutton
        16. Tag
        17. TextArea
        18. TextLine
        19. Time
        1. Field set
        2. Item set
        3. Option set
      1. Mixins
      2. Localization
      3. Styles
    2. Content Types
    3. X-data
    4. Macros
      1. Pages
      2. Regions
      3. Part component
      4. Layout component
      5. Text component
      6. Component Filtering
      7. Component Indexing
    1. Marketplace
    2. Market guidelines

Highlighting

Contents

Highligting was first introduced in version 7.1

Introduction

Highlighters enable you to get highlighted snippets from one or more properties in your search results so you can show users where the query matches are. When you request highlights, the response contains an additional highlight element for each search hit that includes the highlighted properties and the highlighted fragments.

Highlighting options

encoder (string)

Indicates if the snippet should be HTML encoded: default (no encoding) or html.

fragmenter (string)

Specifies how text should be broken up in highlight snippets: simple or span (default).

fragmentSize (number)

The size of the highlighted fragment in characters. Defaults to 100.

numberOfFragments (number)

The maximum number of fragments to return. If numberOfFragments is 0, no fragments will be returned and fragmentSize will be ignored. Defaults to 5.

noMatchSize (number)

The amount of characters you want to return from the beginning of the property if there are no matching fragments to highlight. Defaults to 0 (nothing is returned).

order (string)

Sorts highlighted fragments by score when set to score. Defaults to none - will be displayed in the same order in which fragments appear in the property.

preTag (string)

Use in conjunction with postTag to define the HTML tags to wrap the highlighted text. <em> by default.

postTag (string)

Use in conjunction with preTag to define the HTML tags to wrap the highlighted text. </em> by default.

requireFieldMatch (boolean)

Set to false if you want to highlight result in every listed property, regardless it was used in the query or not. Default is true.

tagsSchema (string)

Set to styled to use the built-in tag schema.

Highlighting settings can be set on a global level and then overridden on the property level (except tagsSchema and encoder, these two can be set only on the global layer).

Highlighting Tags

By default, the highlighting will wrap highlighted text inside <em></em> tag. This can be controlled by setting prePag and postTag, for example:

Sample with custom tags

Request:

{
  "query": "fulltext('description', 'house garden')",
  "highlight": {
    "preTag": "<tag1>",
    "postTag": "</tag1>",
    "properties": {
      "description": {}
    }
  }
}

Response:

{
   ...
  "highlight": {
    "c4bb11f1-c6e2-4849-a665-28f612213984": {
      "description": [
        "Traditional <tag1>house</tag1> with big and well maintained <tag1>garden</tag1>."
      ]
    }
  }
}

Encoder

Parameter encoder can be used to define how highlighted text will be encoded. html value will force escaping html, if you use html highlighting tags.

Highlighted Fragments

Each highlighted property can control the size of the highlighted fragment in characters, and the maximum number of fragments to return. On top of this it is possible to specify that highlighted fragments need to be sorted by score. For example:

Sample fragmentSize reducing

Request:

{
  query: "fulltext('description', 'house garden big')",
  highlight: {
    properties: {
      "description": {
        fragmentSize: 15,
        numberOfFragments: 2
      }
    }
  }
}

Response:

{
    ...
  "highlight": {
    "c4bb11f1-c6e2-4849-a665-28f612213984": {
      "description": [
        " <em>house</em> with <em>big</em>",
        " maintained <em>garden</em>."
      ]
    }
  }
}

If number_of_fragments is set to 0 then no fragments are produced, instead the entire content of the property is returned, and of course it is highlighted.

Fragmenter

You can choose between simple (default) and span fragmenters:

Simple Fragmenter

Request:

{
  query: "fulltext('description', 'house garden')",
  highlight: {
    fragmentSize : 15,
    fragmenter: "simple",
    properties: {
      "description": {}
    }
  }
}

Response:

{
    ...
  "highlight": {
    "9922a270-f881-4bf8-be35-189e9a72a4f1": {
      "description": [
        "Traditional <em>house</em> with big and well maintained <em>garden</em>."
      ]
    }
  }
}
Span Fragmenter

Request:

{
  query: "fulltext('description', 'house garden')",
  highlight: {
    fragmentSize : 15,
    fragmenter: "span",
    properties: {
      "description": {}
    }
  }
}

Response:

{
    ...
  "highlight": {
    "9922a270-f881-4bf8-be35-189e9a72a4f1": {
      "description": [
        " maintained <em>garden</em>.",
        " <em>house</em> with big"
      ]
    }
  }
}

Tag Schema

There are also built in "tag" schemas, currently with one single schema called styled with the following tags:

<em class="hlt1">, <em class="hlt2">, <em class="hlt3">,
<em class="hlt4">, <em class="hlt5">, <em class="hlt6">,
<em class="hlt7">, <em class="hlt8">, <em class="hlt9">,
<em class="hlt10">

Require Field Match

requireFieldMatch can be set to false which will cause any property to be highlighted regardless of whether its value matches the query. The default behaviour is true, meaning that only properties that match the query will be highlighted.

Sample with disabled requireFieldMatch property

Request:

{
  query: "fulltext('anyOtherProperty', 'house')",
  highlight: {
    requireFieldMatch: false,
    properties: {
      "description": {}
    }
  }
}

Response:

{
    ...
  "highlight": {
    "c4bb11f1-c6e2-4849-a665-28f612213984": {
      "description": [
        "Traditional <em>house</em> with big and well maintained garden."
      ]
    }
  }
}

Global Settings

Highlighting settings can be set on a global level and then overridden on the property level.

Sample global properties overridden for each property
{
    "query" : {...},
    "highlight" : {
        "numberOfFragments" : 3,
        "fragmentSize" : 150,
        "order": "none",
        "properties" : {
            "displayName" : { "numberOfFragments" : 0 },
            "description" : { "preTags" : ["<tag1>"], "postTags" : ["</tag1>"] },
            "data.address" : { "numberOfFragments" : 5, "order" : "score" }
        }
    }
}

Contents

Contents

AI-powered search

Juke AI