A misplaced `//end::` tag meant that the docs added in #112271 are only
included in the page on fault detection and not the equivalent
troubleshooting docs. This commit fixes the problem.
There is a DLS query referencing a runtime field loaded from _source, when we create the collector manager we retrieve the numDocs which triggers going through all segments and executing the script for each document. StoredFieldSourceProvider relies on leaf ordinals to build an array, but those ordinals are not populated when computing the numDocs via BaseCompositeReader, as that goes through the subreaders contexts, and not the context leaves (there is a subtle difference that bites us there).
Fixes#111637
We should avoid wrapping EsRejectedExecutionException in an
ElasticsearchException as it would change the status code from 429 to
500. Ideally, we should avoid wrapping exceptions altogether, but that
would require bigger changes.
Closes#112106
Basically the same as for nodes that leave the cluster with reason
`disconnected`, except that these disconnects don't involve the master
so don't cause any nodes to leave the cluster.
This commit will remove the "remote_cluster" from the role descriptor of API keys that is sent to elder clusters for RCS 1.0.
This will allow API keys created in 8.15.0 that reference "remote_cluster" to work when sent to an elder cluster.
The API key could either explicitly reference "remote_cluster" or implicitly reference it via the limited by permissions of the superuser built in role.
Note this in reference to the standard API key, not cross cluster API key. The cross cluster API already removes this for elder clusters.
fixes: #112222
related: #107493
* Fix template alias parsing livelock
This commit fixes an issue with templates parsing alias definitions that can cause the ES thread to
hang indefinitely. Due to the malformed alias definition, the parsing gets into a loop which never
exits. In this commit a null check in both the component template and alias parsing code is added,
which prevents the looping.
I have investigated an issue with QA clusters that run release builds. I
wish I could enable query pragmas to confirm the problem instead of
setting up new clusters and replicating data before testing the theory.
This change allows users to enable query pragmas in release builds.
However, due to the risks associated with using pragmas, the
accept_pragma_risks parameter must be explicitly set to true to proceed.
* Semantic reranking should fail whenever inference ID does not exist
* Short circuit text similarity reranking on empty result set
* Update tests
* Remove test - it doesn't do anything useful
* Update docs/changelog/112038.yaml
* Always check crsType when folding spatial functions
* Update docs/changelog/112090.yaml
* Only require capability for fixed test
The other tests passed on older versions anyway.
The info about remote cluster connection modes is a little disjointed.
This commit adds some cross-links between the sections to help users
find more relevant information.
It's not obvious from the docs that transport connections (including
connections to remote clusters) use a custom binary protocol and require
a _layer 4_ proxy. This commit clarifies this point.
* (Doc+) Link API to parent Doc part1
---------
Co-authored-by: shainaraskas <shaina.raskas@elastic.co>
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
This changes the generated types tables in the docs to say `date`
instead of `datetime`. That's the name of the field in Elasticsearch so
it's a lot less confusing to call it that.
Closes#111650
* No error for store_array_source in standard mode
* Update docs/changelog/111966.yaml
* nested object test
* restore noop tests
* spotless fix
(cherry picked from commit 9ab8665235)
#111943 unveiled a bug in `collectChilder` where we attempt to collect
the previous doc of the parent, even when the parent doc has no previous
doc.
Fixes#111990, #111991, #111992, #111993
The node-disconnected exception might not include the root cause. In
this case, the failure collector incorrectly unwraps the exception and
wraps it in a new Elasticsearch exception, losing the message. We should
instead use the original exception to preserve the reason.
Closes#111894
This adds some basic documentation for the `profile` option in ESQL but
doesn't really explain the results beyond "this is for human debugging."
We're not ready for any kind of specification for this thing, but it is
useful to look at.
