Dynamic Field Naming Conventions and Definitions

Created on 21 September 2023, about 1 year ago

I'm reviewing the available dynamic fields and the distinction between some are unclear.

For example, these two:

<dynamicField name="tcedgem_*" type="text_edge" stored="true" indexed="true" multiValued="true" termVectors="true" omitNorms="false" />
<dynamicField name="tucedgem_*" type="text_edge" stored="true" indexed="true" multiValued="true" termVectors="true" omitNorms="false" />

I read the names to mean "text edge multivalue" fields but what does the "c" and "uc" stand for in the names tcedgem_ and tucedgem_? Unstemmed? Collated?

Reasoning for asking: I store external, non-Drupal content in our Solr index for cross site search. I try to reuse fields when possible and try to match the purpose of the generated field definitions.

πŸ’¬ Support request
Status

Closed: works as designed

Version

4.2

Component

Documentation

Created by

πŸ‡ΊπŸ‡ΈUnited States rblackmore

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @rblackmore
  • πŸ‡©πŸ‡ͺGermany mkalkbrenner πŸ‡©πŸ‡ͺ

    ts: text single
    tm: text multiple
    tus: text unstemmed single
    tum: text unstemmed multiple
    tos: text oomit norms single
    tom: text oomit norms multiple
    tc...s: text custom ... single
    tc...m: text custom ... multiple
    tuc...s: text unstemmed custom ... single
    tuc...m: text unstemmed custom ... multiple

    For edge ngram there's no unstemmed variation, but the field exists for compatibility.
    Custom types are those which are are variations of the default text field Search API provides. You can add new fields or modify existing ones using all configuration options Solr provides. The edge ngram filter is such an option.

  • πŸ‡ΊπŸ‡ΈUnited States rblackmore

    Perfect. Thank you!

  • Status changed to Closed: works as designed about 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States rblackmore
Production build 0.71.5 2024