You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/release-notes/highlights-6.4.0.asciidoc
+17
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,22 @@ See also <<release-notes-6.4.0,{es} 6.4.0 release notes>>.
15
15
* Korean analysis tools - A new plugin has been added which provides analysis tools for the Korean language. The new `nori` analyzer can be used to analyze Korean text "out of the box" and custom analyzers can use a tokenizer, part of speech token filter and a Hanja reading form token filter. For more information, see {plugins}/analysis-nori.html[Nori Plugin].
16
16
* Add multiplexing token filter - This new token filter allows you to run tokens through multiple different tokenfilters and stack the results. For example, you can now easily index the original form of a token, its lowercase form and a stemmed form all at the same position, allowing you to search for stemmed and unstemmed tokens in the same field. For more information, see <<analysis-multiplexer-tokenfilter,Multiplexer token filter>>.
17
17
18
+
[float]
19
+
=== Machine learning
20
+
21
+
* Improve your machine learning results with custom rules. If you want to fine
22
+
tune your machine learning results (for example, to skip anomalies related to
23
+
certain servers), you can now create custom rules in {kib} and by using {ml} APIs.
24
+
Custom rules instruct anomaly detectors to change their behavior based on
25
+
domain-specific knowledge that you provide. See
26
+
{stack-ov}/ml-configuring-detector-custom-rules.html[Customizing detectors with custom rules]
27
+
* The {ml} analytics can now detect specific change points in a time series,
28
+
such as step changes, linear scaling, and time shifts (for example, related to
29
+
daylight savings). There is also a new probability model that can predict when
30
+
step changes might occur. As a result, the {ml} results are more robust and can
31
+
make more accurate predictions when these types of changes are present in your
32
+
data.
33
+
18
34
[float]
19
35
=== Mappings
20
36
@@ -41,3 +57,4 @@ changes ranges include https://github.com/elastic/elasticsearch/pulls?q=is%3Aclo
41
57
42
58
Specifically we want to highlight the https://github.com/elastic/elasticsearch/pull/30414[added support for AWS session tokens] to both
43
59
the EC2 discovery plugin and the S3 repository plugins. This allows Elasticsearch to use AWS devices protected by multi factor authentication.
0 commit comments