Version 9.2.14

Released: March 28th 2025

Minor changes

• Commit fe94 Implemented --mockstack flag to calculate recursive operation stack requirements. The new --mockstack mode analyzes and reports the necessary stack sizes for recursive expression evaluation, pttern matching operations, filter processing. Calculated stack requirements are output to console for debugging and optimization purposes.
• Issue #3058 Enabled boolean_simplify by default.
• Issue #3172 Added a new config option: searchd.kibana_version_string, which can be useful when using Manticore with specific versions of Kibana or OpenSearch Dashboards that expect a particular Elasticsearch version.
• Issue #3211 Fixed CALL SUGGEST to work with 2-character words.
• Issue #490 Improved fuzzy search: previously, it couldn't sometimes find "defghi" when searching for "def ghi" if another matching document existed.
• ⚠️ BREAKING Issue #3165 Changed _id to id in some HTTP JSON responses for consistency. Make sure to update your app accordingly.
• ⚠️ BREAKING Issue #3186 Added a check for server_id during cluster joins to ensure each node has a unique ID. The JOIN CLUSTER operation can now fail with an error message indicating a duplicate server_id when the joining node has the same server_id as an existing node in the cluster. To resolve this issue, ensure that each node in the replication cluster has a unique server_id. You can change the default server_id in the "searchd" section of your configuration file to a unique value before attempting to join the cluster. This change updates the replication protocol. If you are running a replication cluster, you need to:
  • First, cleanly stop all your nodes
  • Then, start the node that was stopped last with --new-cluster, using the tool manticore_new_cluster in Linux.
  • Read about restarting a cluster for more details.

Bugfixes

• Commit 6fda Fixed a crash caused by losing the scheduler after a wait; now, specific schedulers like serializer are properly restored.
• Commit c333 Fixed a bug where weights from the right joined table couldn't be used in the ORDER BY clause.
• Issue #2644 gcc 14.2.0: fixed lower_bound call error with const knn::DocDist_t*&. ❤️ Thank you @Azq2 for the PR.
• Issue #3018 Fixed an issue with handling uppercase table names during auto-schema inserts.
• Issue #3119 Fixed a crash when decoding invalid base64 input.
• Issue #3121 Fixed two related KNN index issues on ALTER: float vectors now keep their original dimensions, and KNN indexes are now properly generated.
• Issue #3123 Fixed a crash when building a secondary index on an empty JSON column.
• Issue #3138 Fixed a crash caused by duplicate entries.
• Issue #3151 Fixed: fuzzy=1 option couldn't be used with ranker or field_weights.
• Issue #3163 Fixed a bug where SET GLOBAL timezone had no effect.
• Issue #3181 Fixed an issue where text field values could be lost when using IDs larger than 2^63.
• Issue #3189 Fixed: UPDATE statements now correctly respect the query_log_min_msec setting.
• Issue #3247 Fixed a race condition when saving real-time disk chunks that could cause JOIN CLUSTER to fail.