Release changes to schemas
While upgrading your schema customizations, note the following changes to the Product, Attribute and Category schemas.
9.1.18.0 release changes
- ElasticSearch Schema
- Global_sequence will be used to sequence products for expanded navigation in the sales and master catalogs. A new global_sequence.sequence field has been introduced to both the E-site and CAS product schemas. This product sequence will be followed at each level of the category, depending on the sort filter. The product index comprises global_sequences for each catalog-category.
9.1.17.0 release changes
- ElasticSearch Schema
- Added a new analyzer named custom_suggestion with the tokenizer as standard so that our whitespace customisation in the case of custom_analyzer does not affect the behavior of our suggestion API.
9.1.16.0 release changes
- ElasticSearch Schema
- No changes.
9.1.15.2 release changes
- ElasticSearch Schema
-
- Added dynamic template for facets.normalized,facets.raw,facets.key,global_sequence_catalog_category, and default.search.path_name_<locale> in both cas_product_elastic_schema.json and product_elastic_schema.json.
- Changed the types of facets and filtersfields to conditional based on the flow.index.flattened ingest configuration in both cas_product_elastic_schema.json and product_elastic_schema.json.
- Stopped copying path_name.string into the default.search.text field in both cas_product_elastic_schema.json and product_elastic_schema.json.
- Stopped copying name.store.text, description.store.text and keyword.store.normalized into the default.suggestion field in cas_product_elastic_schema.json.
9.1.15.1 release changes
- ElasticSearch Schema
-
- Added dynamic_template keyword.<store>.normalized and updated the field default.correction type from object to text in cas_product_elastic_schema.json.
- Added field keyword.normalized and dynamic_template keyword.override.normalized in product_elastic_schema.json.
- Added custom analyzer custom_<locale>_stemmer_override in both cas_product_elastic_schema.json and product_elastic_schema.json.
9.1.15 release changes
- ElasticSearch Schema
-
- Addition of fields in
log_dynamic_mappings.json:
Added fields history and language in log_dynamic_mappings.json to include change history event IDs in the run response.
- New filters and custom analyzer in
cas_product_elastic_schema.json:
Introduced the pattern_replace_char_filter and whitespaces_replace_char_filter filters.
Implemented a custom analyzer named es_pattern_replace for the sku and mpn fields in cas_product_elastic_schema.json.
- Addition of fields in
log_dynamic_mappings.json:
9.1.14.1 release changes
- ElasticSearch Schema
- No Change.
- NiFi Pipeline
- Added WaitLink - Product Stage 1a[WaitLink],
WaitLink - Enrich NLP[WaitLink], and moved
Enrich NLP[NLPStage1] after WaitLink -
Product Stage 1g[WaitLink] in the
dataload.product.casconnector.
9.1.14 release changes
- ElasticSearch Schema
-
- Tokenizer switch in custom_splitter
analyzer:
Implemented a switch in the tokenizer used by the custom_splitter analyzer from keyword to whitespace in cas_product_elastic_schema.json.
- New Split field addition in
search index mapping:
Introduced a new split field in the search index mapping of cas_product_elastic_schema.json with specific settings tailored for text analysis.
- Tokenizer switch in custom_splitter
analyzer:
9.1.13.3 release changes
- ElasticSearch Schema
-
- Catalog filter enhancement:
Added support for base contract inheritance for catalog filters by introducing a new child field in store_dynamic_mappings.json.
- Default stemmer change to Snowball:
Changed the default stemmer in cas_product_elastic_schema.json and product_elastic_schema.json from the existing one to the Snowball stemmer.
- Catalog filter enhancement:
9.1.13.2 release changes
- ElasticSearch Schema
- No changes.
9.1.13.1 release changes
- ElasticSearch Schema
-
- New field addition:
Added a new field named key inside attribute.value in both cas_product_elastic_schema.json and product_elastic_schema.json.
- New field addition:
9.1.13.0 release changes
- ElasticSearch Schema
-
- Natural keyword field mapping:
Modified the cas_product_elastic_schema.json and product_elastic_schema.json to include natural keyword field mapping.
- Asset store schema addition:
Introduced the asset_store to the store_dynamic_mappings.json.
- Text property details addition:
Added text property details for default.correction in product_elastic_schema.json.
- Parent field inclusion:
Under the name and description fields in product_elastic_schema.json, a new parent field has been added.
- Natural keyword field mapping:

9.1.12.0 release changes
- Product Schema
-
- The new field deep_published was added.
- The new field default.sku was added.
- The default.sku.normalized field is added in
copy_tosection of sku.parent and sku.normlized fields. - A new analyzer, custom_analyzer was added.
- The type
objectof property name was removed and the propertiesnormalized, raw, split, shingledwere added. - The type
objectof property description was removed and the properties normalized, raw. - The type
objectof property keyword was removed and and the propertiesoverride, textwere added. - The type
objectof property default.search was removed and the propertiestext, normalizedwere added. - The type
objectof property default.noun was removed and the propertiesraw, normalizedwere added. - The type
objectof property default.adjective wasand the propertiesraw, normalizedwere added. - The type
objectof property default.names was removed and the propertiesraw, normalizedwere added. - A new field, path_name, was added.
- Attribute Schema
- The type
objectof propertynamewas removed and propertiesnormalizedandrawwere added. - Category Schema
- The type
objectof property name was removed and propertiesnormalizedandrawwere added. - General changes related to Analyzer, Filter, and Normalizer which are applicable to multiple schema
-
-
New analysers added. These analysers use different tokenizers
and filters, which are applied to different index fields to perform
text analysis processing on terms during ingestion and at index
time, and during query processing and search runtime.
- custom_splitter: Uses keyword tokenizer. Added in product schema.
- custom_shingle: Uses standard tokenizer. Added in product schema.
- custom_analyzer: Uses standard tokenizer. Added in Attribute Schema, catalog schema, category schema, product schema.
- New Filters added. The following Elasticsearch filters can be
used inside custom analyzers to convert (for example, normalize or
pre-process) the index field values for use in the Elasticsearch
index.
- html_strip: Strips html elements from text and replaces html entities with their decoded values. Added in Attribute schema , catalog schema, category schema, product schema, product schema.
- word_delimiter_filter: Splits tokens at non-alphanumeric characters. Added in the product schema.
- shingled_filter: Adds shingles, or word n-grams, to a token stream by concatenating adjacent tokens. Added in product schema.
- trim_filter: Removes leading and trailing whitespace from each token in a stream. Added in product schema.
- special_char_filter: It maps special char mapping as per the mappings mentioned in the filter. Added in Attribute Schema , catalog Schema,category schema.
- The normalizer property has changed from
lowercasetonormalized, because it not only changes the word to lowercase but also performs ASCII folding. This normalizer is used in all normalized index fields. This change is applicable to the Attribute Schema , catalog schema,category schema, description schema,store schema, and workspace schema.
-
New analysers added. These analysers use different tokenizers
and filters, which are applied to different index fields to perform
text analysis processing on terms during ingestion and at index
time, and during query processing and search runtime.

9.1.11.0 release changes
- Product Schema
-
- A new field, has_sku, has been added.
-
In manufacture.text and seller.text, a
copy_tosection has been added, with the following structure.."copy_to": [ "default.search.text", "default.correction.text", "default.completion", "default.suggestion" ]
- Category Schema
- No Change.