-
Notifications
You must be signed in to change notification settings - Fork 25.5k
[docs] Logs Index Mode - copy paste friendly settings #124293
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
Co-authored-by: shainaraskas <[email protected]>
* Fix NPE by getting request once and defaulting to empty list * Fix error in OpenAIUpgrade test which used the wrong field name for certain versions * [CI] Auto commit changes from spotless --------- Co-authored-by: elasticsearchmachine <[email protected]>
This updates the gradle wrapper to 8.12 We addressed deprecation warnings due to the update that includes: - Fix change in TestOutputEvent api - Fix deprecation in groovy syntax - Use latest ospackage plugin containing our fix - Remove project usages at execution time - Fix deprecated project references in repository-old-versions (cherry picked from commit ba61f8c) # Conflicts: # build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/distribution/DockerUbiElasticsearchDistributionType.java # build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/test/Fixture.java # plugins/repository-hdfs/hadoop-client-api/build.gradle # qa/entitlements/build.gradle # server/src/main/java/org/elasticsearch/indices/IndicesFeatures.java # x-pack/plugin/migrate/build.gradle # x-pack/plugin/security/qa/security-basic/build.gradle
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes #118329 (cherry picked from commit f028340)
The STABLE_CONFIGURATION_CACHE feature flag enables the following: - tasks using a shared build service without declaring the requirement via the Task.usesService method will emit a deprecation warning. - when the configuration cache is not enabled but the feature flag is present, deprecations for the following configuration cache requirements are also enabled: - Registering build listeners - Using task extensions and conventions at execution time
#119469) Co-authored-by: Joe Gallo <[email protected]>
…o 2503e99 (#119414) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
…19516) (#119527) * fix: do not let `_resolve/cluster` hang if remote is unresponsive Previously, `_resolve/cluster` would wait for a response from a remote as part of the connection strategy. If the remote were to be unresponsive, this API would wait until `netty` would terminate the connection with a handshake exception. The threshold for terminating the connection is `10s`. This means that the API would wait for `10s` before determining that the remote is unresponsive. This strategy is now replaced with a fail fast where a response is sent back to the user immediately rather than waiting for a connection termination. * Update docs/changelog/119516.yaml
* Refactor change point detection (#114289) * Move change detection code to separate class * Uniformize ChangeDetector and SkipeAndDipDetector * Separate ChangeDetectorTests and ChangePointAggregatorTests. * Public entrypoint for change point detection * Move p-value computation to ChangeDetector * Move main entrypoint to a separate file * Fix change point detection for uncertain non-stationary distributions. (#119578) * Fix change point detection for uncertain non-stationary distributions. * Replace -1 by ChangeType.NO_CHANGE_POINT
I believe this is a typo, as in our 8.16.1 cluster this field appears to be called `combined_coordinating_and_primary`
…uginFuncTest supports linux aarch distributions #119868
…uginFuncTest bwc expanded distribution folder can be resolved as bwc project artifact #119869
bad link generation for github issue
In the 8.17 docs there is a statement that intends to say that nodes without roles are coordinating-only nodes. However, the wording was misleading because it referred to leaving the setting _unset_ rather than explictly setting it to _empty_.
* Fix Gradle Deprecation warning as declaring an is- property with a Boolean type has been deprecated. * Make use of new layout.settingsFolder api to address some cross project references * Fix buildParams snapshot check for multiprojet projects (cherry picked from commit e19b226) # Conflicts: # build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/BaseInternalPluginBuildPlugin.java # docs/build.gradle # qa/entitlements/build.gradle # x-pack/qa/multi-project/core-rest-tests-with-multiple-projects/build.gradle # x-pack/qa/multi-project/xpack-rest-tests-with-multiple-projects/build.gradle
(cherry picked from commit 590b75d) Co-authored-by: David Kyle <[email protected]>
…) (#124267) # Backport This will backport the following commits from `main` to `8.17`: - [Avoid hoarding cluster state references during rollover (#124107)](#124107) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)
make settings more copy/paste friendly
Documentation preview: |
@LucaWintergerst please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
This should normally be submitted to |
ok - I got lazy and just used the edit button on the docs page. |
make settings more copy/paste friendly
I am not sure if we generate parts of this (the list at the bottom), but I'd like to make some of these more copy/paste friendly so I can copy them into Devtools or similar and don't have to add quotes.