Elasticsearch 7.8.1 Release Highlights and New Features
Elasticsearch 7.8.1 introduces a range of new capabilities such as literal SUM/MIN/MAX/AVG in SQL, enhanced authorization for apm_user, updated index creation logging, composable template renaming, additional machine‑learning aggregations, snapshot/restore optimizations, and an improved update API, all aimed at boosting search and analytics performance.
Elasticsearch is a distributed, RESTful search and data‑analysis engine that serves as the core of the Elastic Stack, centralizing data storage and helping users discover both expected and unexpected insights.
It provides real‑time, distributed search and analytics, enabling exploration of data at unprecedented speed and scale, and is used for full‑text search, structured search, analytics, and combinations of these functions.
New Features
SQL
Support literal SUM, MIN, MAX, AVG expressions.
Improvements
Authorization
Add read privilege for apm_user observability annotations.
Features/Indices APIs
Change "apply create index" log level to DEBUG.
Make noop template updates a cluster‑state noop.
Rename template V2 class to ComposableTemplate.
Machine Learning
Add exponential moving average aggregator to inference.
Snapshot/Restore
Allow read operations without waiting for the entire range to be written to cache.
Enable SparseFileTracker to execute listeners incrementally during gap handling.
Allow CacheFile to use re‑entrant R/W lock without ReleasableLock wrapper.
Build searchable snapshot storage metadata using snapshot information (MetadataSnapshot).
Transform
Improve the update API.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Laravel Tech Community
Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
