2.10.19.2

[rbayet]

Main features

Additional KPIs in Analytics > Search Usage

KPIs about category views, product views, products added to cart and sales event are now extracted from your behavioral data and visible in the "Analytics > Search Usage dashboard".

Removal of the hardcoded 'sku' field from exact queries filtering part

Historically, when filtering (not scoring !) results, exact match queries always targeted at least the search collector field (containing all searchable attributes content) and the sku field, whatever search weight was assigned to the sku field.
As

• on one hand, we have introduced back in releases 2.10.17 and 2.11.3 (experimental) settings to specifically target in that filtering query part all fields using the reference search analyzer (used by the sku attribute by default)
• on the other hand, you might be in a situation where you do not want at all the sku to be searchable

we have decided to remove that hardcoded sku in exact queries filtering part.

Long story short, if your users frequently perform searches by SKU and you're still using the reference analyzer for that attribute, we urge you to go enable the following Search Relevance settings listed below :

• Elasticsuite > Search Relevance > Spellchecking Configuration > Term Vectors Configuration > Use all tokens from term vectors
• Elasticsuite > Search Relevance > Spellchecking Configuration > Term Vectors Configuration > Use reference analyzer in term vectors
• Elasticsuite > Search Relevance > Relevance Configuration > Exact matching configuration > Use default analyzer in exact matching filter query

Ability to set custom number of primary shards and replicas by index type

If you're using a 3 nodes cluster in your production environment, you could have been tempted to set 3 primary shards and 2 replicas in the legacy Elasticsuite base settings.
While it is our opinion that having multiple primary shards is hardly necessary unless you really have a sizeable product index, it is now possible to go this route while keeping usually light indices (categories, thesaurus, and tracker indices on low traffic sites) with a single primary shard.
It is now possible to definer per index type the number of primary shards and replicas of indices.

This will allow you to minimize the memory footprint per node of opened shards/indices in your cluster (the rule of thumb being that 1 GB of Heap is required per node per 20 shards just for those indices being opened).

Admin notifications about invalid tracker events and automated removal

Releases 2.10.18.3 and 2.11.4.3 introduced some protections to avoid indexing invalid tracker events missing unique visitor or session ids into the behavioral data indices (as well as CLI tools to remove those already indexed).
Those invalid tracker events were left in the Elasticsuite tracker DB table with a flag is_invalid = 1.
This release introduces a cronjob task that will automatically and periodically remove them and a notification system to warn you about their existence (if you want to investigate the potential issue in your tracker tags).

You also have the ability to remove all of them at once.

📦 Features

• [Analytics] Additional product/category/sales KPIs by @rbayet in [Analytics] Additional product/category/sales KPIs #3214
• [Config] Make getIndicesSettingsConfigParam public. by @rbayet in [Config] Make getIndicesSettingsConfigParam public. #3195
• [Core] Feature custom number of shards replicas by @romainruaud in Feat custom number of shards replicas #3185
• [Core] Append default CONFIG cache tag to ES configuration and also a generic ES cache tag by @romainruaud in Append default CONFIG cache tag to ES configuration and also a generi… #3191
• [Core] Enable Elasticsuite ES cache tag automatically. by @romainruaud in Enable Elasticsuite cache tag automatically. #3197
• [Cache] Add cache on search query building by @PierreGauthier in Add cache on search query building #3193 and Add cache on search query building #3213
• [Search] Allow configurable msm for fuzzy search by @rbayet in [Search] Allow configurable msm for fuzzy search #3196
• [Search] Remove hardcoded SKU from query builder since new options should allow to explicitely target it by @romainruaud in Remove hardcoded SKU from query builder since new options should allo… #3198
• [Tracker] Automated removal of queued invalid events by @rbayet in [Tracker] Automated removal of queued invalid events #3204

🐛 Fixes

• [Optimizer] Clean Applier Definition by @PierreGauthier in [Optimizer] Clean Applier Definition #3181
• [Spellchecker] Fix multi index by alias error by @PierreGauthier in Spellchecker : Fix multi index by alias error #3199
• [Tracker] Ensuring tracker provided store_id is numeric. by @romainruaud in Fix #3157 by ensuring store_id is numeric. #3187

🧰 Quality

• [Quality] Spellchecker unit tests by @rbayet in [Quality] Spellchecker unit tests #3207

Full Changelog: 2.10.19.1...2.10.19.2

---

This discussion was created from the release 2.10.19.2.