Not all string-fields need to be analyzed and sortable

[majsan]

For the ES mapping, if the configuration says: "type": "string", we use multi-fields to add a raw field (with no analysis at all) and a sort field with icu_collation_keyword type, used for sorting.

Some fields that are of string type do not need sorting or analysis.

If anaysis is not needed, use "type": "keyword" in the Elasticsearch mapping and skip the raw-field.

If there is no need to sort, do not add sort-field. Also, sorting might need more configuration in the future, in case we have fields with other sorting rules.

The question is how to do this in our configuration. Maybe type can accept an object instead of a string when the type needs more configuration. For example:

"type": {
    "name": "string",
    "analysis": false,
    "sorting": false
}

[majsan]

Simply "type": "keyword"?

[majsan]

Salex internal ID fields should use this type and also the coming internal field _id (see the internal field _entry_version etc) so that users can search for equals|@id|ABC123.