-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Backfill changelogs for 8.1.0 #83341
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
Conversation
Pinging @elastic/es-delivery (Team:Delivery) |
@ywelsch you have some PRs labelled |
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.
One minor comment, otherwise LGTM.
...d-tools-internal/src/main/java/org/elasticsearch/gradle/internal/release/ChangelogEntry.java
Outdated
Show resolved
Hide resolved
@elasticmachine run elasticsearch-ci/docs |
Removing this while we get the 8.2 migration guide in place in elastic/elasticsearch#83341
@elasticmachine run elasticsearch-ci/docs |
It looks like I pushed elastic/stack-docs@83a16f2 to swap it back. I don't know if there's a good way to prevent this in the future, but it may be something we want to document. |
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 overall. I left a couple of minor nits, and an edit for @ywelsch.
Thanks for putting this together!
* Copy `trace.id` in threadcontext stash {es-pull}83218[#83218] | ||
|
||
Infra/Scripting:: | ||
* Fix duplicated allow lists upon script engine creation {es-pull}82820[#82820] (issue: {es-issue}82778[#82778]) |
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.
Should this one be here? It looks to be 8.0.0-rc2.
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 went trawling through git for this, and I can only find the commit on the 8.1
and master
branches, but it doesn't exist on 8.0
, so I have to assume the change didn't actually make it into the branch that the labels claim. This is why we need the new process 👍
docs/changelog/80024.yaml
Outdated
- 80021 | ||
area: Search | ||
type: enhancement | ||
summary: Support combining `_shards` preference param with <custom-string> |
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.
summary: Support combining `_shards` preference param with <custom-string> | |
summary: Support combining `_shards` preference param with `<custom-string>` |
docs/changelog/82409.yaml
Outdated
Doc-value-only fields allow users to trade slower query performance for | ||
an increased indexing rate and storage space efficiency. This is | ||
achieved by disabling inverted structures such as the inverted index or | ||
points, and using the columnar storage format of doc values to run | ||
queries instead, while still providing the same usual great performance | ||
for aggregating and sorting data. {es} {version} supports term and | ||
range queries on `numeric`, `date`, `keyword`, `ip`, and `boolean` | ||
doc-value-only field types. |
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.
@ywelsch Let me know what you think of these changes. I tried to address two minor issues:
- I wasn't sure if "date" included
date_nanos
. It does, but it wasn't clear from this text. - I'm not sure we needed the info about the internal data structures and storage formats. Those felt like implementation details to me and are a little redundant with the doc value docs, but let me know what you think.
Doc-value-only fields allow users to trade slower query performance for | |
an increased indexing rate and storage space efficiency. This is | |
achieved by disabling inverted structures such as the inverted index or | |
points, and using the columnar storage format of doc values to run | |
queries instead, while still providing the same usual great performance | |
for aggregating and sorting data. {es} {version} supports term and | |
range queries on `numeric`, `date`, `keyword`, `ip`, and `boolean` | |
doc-value-only field types. | |
You can now run `term` and `range` queries on numeric, `date`, `date_nanos`, | |
`keyword`, `ip`, and `boolean` fields that only store doc values. | |
In exchange for slower queries, doc-value-only fields offer: | |
* Increased indexing rates | |
* Better storage efficiency | |
* Great performance for aggregating and sorting data | |
For more information about doc values, refer to the | |
{ref}/doc-values.html[`doc_values` mapping parameter documentation]. |
I'd be great if we had a mapping example of a doc-value-only field we could link to from here.
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.
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.
Awesome. Thanks, @ywelsch!
docs/changelog/82409.yaml
Outdated
# this support | ||
highlight: | ||
notable: false | ||
title: Doc-values-only search is now supported on numeric, date, keyword, ip, and boolean types |
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.
title: Doc-values-only search is now supported on numeric, date, keyword, ip, and boolean types | |
title: Doc-values-only search on numeric, `date`, `date_nanos`, `keyword`, `ip`, and `boolean` fields |
964ca7a
to
33e5876
Compare
Forward-port of the `build-tools-internal` parts of elastic#83341.
Forward-port of the `build-tools-internal` parts of #83341.
We want to use the new release notes generation process for 8.1.0. In order to do that, we need to backfill the
docs/changelog
directory with YAML files, to account for the time period up until we started generating YAMLfiles for all applicable PRs.
Also:
Breaking
class for both. Note that this will require a HOMER change as well.I intend to do another pass before 8.1.0 is released, in order to check that we haven't missed any PRs that ought to have YAML files, and to ensure we don't have any lurking files that ought to have been removed.