-
Notifications
You must be signed in to change notification settings - Fork 25.6k
release notes for 6.8.3 #46157
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
release notes for 6.8.3 #46157
Conversation
|
Pinging @elastic/es-docs |
| * Use system context for looking up connected nodes {pull}43991[#43991] (issue: {issue}43974[#43974]) | ||
|
|
||
| Machine Learning:: | ||
| * [DOCS] Adds allow no datafeeds query param to the GET, GET stats and STOP datafeed APIs (7.2-6.1) {pull}44864[#44864] |
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 one should be omitted. I've added the >docs label to the PR
| * Include leases in error message when operations no longer available {pull}45681[#45681] | ||
|
|
||
| Infra/Core:: | ||
| * Add OCI annotations and adjust existing annotations {pull}45167[#45167] (issues: {issue}45162[#45162], {issue}45166[#45166]) |
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 think 45162 and 45166 are related PRs, not issues.
| * Ensure AsyncTask#isScheduled remain false after close {pull}45687[#45687] (issue: {issue}45576[#45576]) | ||
|
|
||
| Engine:: | ||
| * Handle delete document level failures {pull}46100[#46100] (issue: {issue}46083[#46083]) |
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.
Likewise, I think 46083 is a related PR, not an issue fixed by 46100
| * Handle no-op document level failures {pull}46083[#46083] | ||
|
|
||
| Features/Indices APIs:: | ||
| * Check shard limit after applying index templates {pull}44619[#44619] (issues: {issue}34021[#34021], {issue}44567[#44567], {issue}44619[#44619]) |
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.
Likewise, I think 34021 is just a related PR not a fixed issue.
The 44619 also appears twice here--once as a PR and once as an issue.
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.
It looks like the script is treating all "Relates" and "Supersedes" references as issues. (The duplicate entry is because the Supersedes reference is referencing the same PR.)
| * Add rest_total_hits_as_int in HLRC's search requests {pull}46076[#46076] (issue: {issue}43925[#43925]) | ||
|
|
||
| Infra/Core:: | ||
| * Add default CLI JVM options {pull}44545[#44545] (issues: {issue}219[#219], {issue}42021[#42021]) |
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.
It seems to me that #219 is unrelated
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.
It was a reference to an issue in elasticsearch-docker.
|
@elasticmachine, run elasticsearch-ci/docs |
debadair
left a comment
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.
LGTM, except the xref weirdness that @lcawl caught.
| * Add rest_total_hits_as_int in HLRC's search requests {pull}46076[#46076] (issue: {issue}43925[#43925]) | ||
|
|
||
| Infra/Core:: | ||
| * Add default CLI JVM options {pull}44545[#44545] (issues: {issue}219[#219], {issue}42021[#42021]) |
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.
It was a reference to an issue in elasticsearch-docker.
| * Handle no-op document level failures {pull}46083[#46083] | ||
|
|
||
| Features/Indices APIs:: | ||
| * Check shard limit after applying index templates {pull}44619[#44619] (issues: {issue}34021[#34021], {issue}44567[#44567], {issue}44619[#44619]) |
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.
It looks like the script is treating all "Relates" and "Supersedes" references as issues. (The duplicate entry is because the Supersedes reference is referencing the same PR.)
lcawl
left a comment
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.
Thanks @pcsanwald I didn't click every link, but it LGTM. Hope you're feeling better!
6.8.3 release notes.