Product Selector

Fusion 5.9
    Fusion 5.9

    Solr Dynamic Field Name MappingIndex pipeline stage configuration specifications

    Table of Contents

    This stage can be used to re-name existing fields to match Solr dynamic field names, so that they will be typed correctly by Solr. It also can be used to specify fields which should be exempt from name changes as well as to set the dynamic type suffixes to a specified field. Note that the field that is processed by a Field Mapping stage prior to this stage will not be renamed, even if the stage config matches the field name.

    Configuration

    When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.

    Map pipeline document fields to a Solr dynamic fields

    skip - boolean

    Set to true to skip this stage.

    Default: false

    label - string

    A unique label for this stage.

    <= 255 characters

    condition - string

    Define a conditional script that must result in true or false. This can be used to determine if the stage should process or not.

    duplicateSingleValuedFields - boolean

    This option enables indexing of a field data into both single-valued and multi-valued Solr fields. For example, a field 'phone' hinted as a "string" type and containing only one value will be indexed into a 'phone_s without this option enabled. However, if the option is enabled, the 'phone' field will be indexed into both 'phone_s' (single-valued) and 'phone_ss' (multi-valued) fields.

    Default: false

    fieldsToExclude - array[string]

    The list of Pipeline Document fields to exclude from processing.

    advancedTextFieldsIndexing - boolean

    This option enables indexing of a text data (not exceeding certain max length) into both tokenized and non-tokenized fields. For example a field 'name' containing "John Smith", if not hinted or finalized in previous stages, without this option enabled will be indexed into a "text" type field by default (name_t). But if the option is enabled, it will be indexed into both 'name_t' and 'name_s' fields allowing relevant search using 'name_t' field (by matching to a 'Smith' query) and also proper faceting and sorting using 'name_s' field (using value 'John Smith' for sorting or faceting).

    Default: true

    maxTextLengthForAdvancedIndexing - integer

    Default: 100