This PR contains the following updates:
| Package | Update | Change | |---|---|---| |
docker.elastic.co/wolfi/chainguard-base | digest | `c16d3ad` ->
`90888b1` |
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once
you are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Renovate
Bot](https://togithub.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
* Add chunking settings configuration to CohereService, AmazonBedrockService, and AzureOpenAiService
* Update docs/changelog/113897.yaml
* Run spotlessApply
* Updating CohereServiceMixedIT to account for clusters without chunking settings in index mapping
---------
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
These test overrides were introduced so that we had somewhere to hang an
`@AwaitsFix` annotation, but now the tests are unmuted again there's no
need for the overrides.
Relates #108336
This method is used in multiple contexts that may not all handle
cluster-block exceptions gracefully, esp. since some types of cluster
blocks are retryable. Removing this, and may follow up with handling the
cluster state block for the affected transport actions instead.
* Adds note on reindexing existing data for semantic_text usage
* Adds note about full crawl and full sync
* Style guide related fix
* Update docs/reference/search/search-your-data/semantic-search-semantic-text.asciidoc
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
---------
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
Today we show `Metadata#clusterUUID` in the response to `GET /`
regardless of whether this value is committed or not, which means that
in theory users may see this value change even if nothing is going
wrong. To avoid any doubt about the stability of this cluster UUID, this
commit suppresses the cluster UUID in this API response until it is
committed.
Including the cluster state in responses to the `POST _cluster/state`
API was deprecated in #90399 (v8.6.0) requiring callers to pass
`?metric=none` to avoid the deprecation warning. This commit adjusts the
behaviour as promised in v9 so that this API never returns the cluster
state, and deprecates the `?metric` parameter itself.
Closes#88978
Today the docs for the `?wait_for_active_shards` parameter say that it
must be a positive integer, proscribing `0`, yet `0` is a legitimate
value for this parameter. This commit fixes this point and rewords the
docs slightly for clarity.
API for `/_inference/{task_type}/{inference_id}/_stream` and `/_inference/{inference_id}/_stream`
Request is `application/json`
Response is `text/event-stream`
Implement and enable streaming for Cohere chat completions (v1).
Includes processor for ND JSON streaming responses.
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Fast refresh indices should now behave like non fast refresh indices in
how they execute (m)gets and searches. I.e., they should use the search
shards.
For BWC, we define a new transport version. We expect search shards to
be upgraded first, before promotable shards. Until the cluster is fully
upgraded, the promotable shards (whether upgraded or not) will still
receive and execute gets/searches locally.
Relates ES-9573
Relates ES-9579
A recent commit incidentally changed a release resources call from
doBefore to doAfter. Several tests depending on resources being released
synchronously which requires doBefore.
Closes#114181Closes#114182
Add support for vectorized ipByteBin.
The structure of the implementation and loading framework mirror that of Lucene, but is simplified by avoiding reflective loading since ES has support for a MRJar section for 21.
For now, we just disable warnings-as-errors in this small sourceset, since -Xlint:-incubating is only support since JDK 22. The number of source files is small here. Will investigate how to assert that just the single incubating warning is emitted by javac, at a later point.
randomInstantBetween can produce a result which is not within the [minInstant, maxInstant] range. This occurs when the epoch second picked matches the min bound and the nanos are below the min nanos, or the second picked matches the max bound seconds and nanos are above the max bound nanos. This change fixes the function by setting a bound on which nano values can be picked if the min or max epoch second value is picked.
Nik Everett
Oleksandr Kolomiiets
David Kyle
elasticsearchmachine
Mike Pellegrini
elastic-renovate-prod[bot]
Dan Rubinstein
Simon Cooper
David Turner
Liam Thompson
Nikolaj Volgushev
Chris Hegarty
ChrisHegarty
Christoph Büscher
kosabogi
Panagiotis Bailis
István Zoltán Szabó
Nick Tindall
Keith Massey
Joe Gallo
Pat Whelan
Iraklis Psaroudakis
Tim Brooks
Rene Groeschke
Kostas Krikellas
Benjamin Trent
Ignacio Vera
moxarth-elastic
Parker Timmins