* Update docs for v8.18.0 release
* Update docs/reference/release-notes/highlights.asciidoc
* Don't lose nice edits, just add net new stuff
* revert highlights to edited version
---------
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
* ESQL: Known issue enrich missing field (#126701)
* Add known issue note to 8.17.0-8.17.4
* Add known issue to 8.16.0-8.16.6
* remove coming tags from notes that hadn't been forward ported to 8.x
* remove another coming tag
* clarify it's esql
* include pages that hadn't been forward ported
---------
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
Co-authored-by: Liam Thompson <leemthompo@gmail.com>
(cherry picked from commit f7a52054b2)
* delete conflict markers on new files to this branch
---------
Co-authored-by: Alexander Spies <alexander.spies@elastic.co>
This commit adds a note that ignore_above has a different limit for
logsdb indices to the documentation. Also specifies that ignore_above
applies to all types of the keyword family.
Relates https://github.com/elastic/sdh-elasticsearch/issues/8892
* Set `keyUsage` for generated HTTP certificates and self-signed CA (#126376)
The `elasticsearch-certutil http` command, and security auto-configuration,
generate the HTTP certificate and CA without setting the `keyUsage` extension.
This PR fixes this by setting (by default):
- `keyCertSign` and `cRLSign` for self-signed CAs
- `digitalSignature` and `keyEncipherment` for HTTP certificates and CSRs
These defaults can be overridden when running `elasticsearch-certutil http`
command. The user will be prompted to change them as they wish.
For `elasticsearch-certutil ca`, the default value can be overridden by passing
the `--keysage` option, e.g.
```
elasticsearch-certutil ca --keyusage "digitalSignature,keyCertSign,cRLSign" -pem
```
Fixes#117769
(cherry picked from commit 284121ad9f)
# Conflicts:
# docs/reference/elasticsearch/command-line-tools/certutil.md
* fix compilation error
* [CI] Auto commit changes from spotless
* fix failing test
---------
Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
* Update missed documentation change for new watcher index settings
* Update docs/reference/rest-api/watcher/update-settings.asciidoc
---------
Co-authored-by: Keith Massey <keith.massey@elastic.co>
* Update service-openai.asciidoc (#125419)
Many customers want to use our OpenAI Inference endpoint against OpenAI compatible API's they have written, or Ollama, or Nvidia Triton OpenAI API front end. I had heard that was the intent of this OpenAI inference endpoint, but we do not state it directly. Can we validate this is OK with Search PM and include this?
Co-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>
* Update docs/reference/inference/service-openai.asciidoc
---------
Co-authored-by: Brad Quarry <38725582+bradquarry@users.noreply.github.com>
* Adds explanation on the delay parameter
* Attribute fixes
* Update docs/reference/transform/usage.asciidoc
---------
Co-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>
added section related to nested bool queries to provide a more clear example and clean up surrounding language and grammatical issues
Co-authored-by: Kofi B <kofi.bartlett@elastic.co>
Clarify that it is expected sometimes to see inter-node connections
sending zero-window advertisements as part of the usual TCP backpressure
mechanism.
Backport of #124967 to 8.x
