-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add 7.3 release highlights. #44153
Add 7.3 release highlights. #44153
Conversation
Pinging @elastic/es-docs |
Pinging @elastic/es-core-infra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some comments
|
||
// tag::notable-highlights[] | ||
[float] | ||
==== Memory leak when using templates in document-level security |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe reword to make clear that the highlight is actually a fix for the potential memory leak? E.g.: "Limit memory usage when ..."?
{xpack-ref}/document-level-security.html[Document-level security] was using an | ||
unbounded cache for the set of visible documents. This could lead to a memory | ||
leaks when using a templated query as a role query. The cache has been fixed to | ||
evict based on memorory usage and has a limit of 50MB. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: memorory
-> memory
==== Aliases are replicated via {ccr} | ||
|
||
Read aliases are now replicated via <<ccr-put-follow,{ccr}>>. Note that write | ||
aliases are still not replicated since they only make since for indices that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"since they only make since" -> "since they only make sense"?
==== Memory leak when using templates in document-level security | ||
|
||
{xpack-ref}/document-level-security.html[Document-level security] was using an | ||
unbounded cache for the set of visible documents. This could lead to a memory |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"This could lead to a memory leak" (singular instead of plural)
@jpountz suggest to add the following items: |
Thanks @yaronp68! |
Co-Authored-By: Tim Vernum <tim@adjective.org>
@jpountz forgot to mention a very big one - support for data frame |
@yaronp68 Added. |
Thanks @yaronp68 ! |
Currently: