Split Notable and Breaking changes, as the notables were appearing to be breaking changes.
(cherry picked from commit 1c1925c16f)
Co-authored-by: David Brimley <dave.brimley@gmail.com>
This adds support for the simple_query_string query type to the Query API key Information API.
In addition, this also adds support for querying all the API Key metadata fields simultaneously,
rather than requiring each to be specified, such as metadata.x, metadata.y, etc.
Relates: #101691
There's a note in the docs saying we only consider shard count and not
disk usage which is no longer true. This commit fixes the note to
reflect today's implementation.
Allow nested expressions to be used both for grouping or inside
aggregate functions inside the stats command.
As such the grammar has been tweaked to allow the stats group to have
optional aliasing.
As part of this fix, preserve the original field declaration (including
spaces) for implicit aliases.
Improve validation for incorrect aggregate function use (as arguments,
grouping or inside evals).
Fix#99828
* [DOCS] Categorize ingest processors on overview page, summarize use cases
* Add overview info, subheading, links
* Apply suggestions from review
Co-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>
* Insert space
---------
Co-authored-by: István Zoltán Szabó <istvan.szabo@elastic.co>
Adds links from the stable master health indicator to the relevant
troubleshooting docs, as well as making the "contact support" link a
versioned link directly to the right subsection of the troubleshooting
docs page.
* Downsampling supports date_histogram with tz
This comes with caveats, for downsampled indexes at intervals more than
15 minutes. For instance,
- 1-hour downsampling will produce inaccurate
results for 1-hour histograms on timezones shifted by XX:30
- 1-day downsampling will produce inaccurate daily
histograms for not-UTC timezones as it tracks days at UTC.
Related to #101309
* Update docs/changelog/103511.yaml
* test daylight savings
* update documentation
* Offset time buckets over downsampled data with TZ
* Update docs/changelog/103511.yaml
* check for TSDS
* fixme for transport version
* add interval to index metadata
* add transport version
* bump up transport version
* address feedbcak
* spotless fix
* added override flag for rename processer along with factory tests
* added yaml tests for rename processor using the override flag
* updated renameProcessor tests to include override flag as a parameter
* updated rename processor tests to incorporate override flag = true scenario
* updated rename processor asciidoc with override option
* updated rename processor asciidoc with override option
* removed unnecessary supresswarnings tag
* corrected formatting errors
* updated processor tests
* fixed yaml tests
* Prefer early throw style here
* Whitespace
* Move and rewrite this test
It's just a simple test of the primary behavior of the rename
processor, so put it first and simplify it.
* Rename this test
It doesn't actually exercise template snippets
* Tidy up this test
---------
Co-authored-by: Joe Gallo <joegallo@gmail.com>
This adds support for the type parameter to the Query API key API.
The type for an API Key can currently be either rest or cross_cluster.
Relates: #101691
This adds unit tests cases for all the functions that were missing tests
checking on the correct generation of the Warning headers in case the
execution raised an Exception that lead to a `null` result.
If a file header is corrupted then the exception may be reported as a
bad index format version rather than a checksum mismatch. This commit
adjusts the docs to cover this case.
Adding a link tag for inner hits behavior and kNN search. Additionally
adding a note that if you are using multiple knn clauses, that the inner
hit name should be provided.
This creates the `MV_FIRST` and `MV_LAST` functions that return the
first and last values from a multivalue field. They are noops from a
single valued field. They are quite similar to `MV_MIN` and `MV_MAX`
except they work on positional data rather than relative size. That
sounds like a large distinction, but in practice our multivalued fields
are often sorted. And when they operate on sorted arrays `MV_MIN` does
*the same* thing as `MV_FIRST`.
But there are some cases where it really does matter - say you are
`SPLIT`ing something - so `MV_FIRST(SPLIT("foo;bar;baz", ";"))` gets you
`foo` like you'd expect. No sorting needed.
Relates to #103879
This commit adds detailed API docs for the ES|QL async apis, as well as moving the narrative to the ES|QL specific REST docs. Additionally, a few top-level lists are reflowed to reflect that there are now multiple APIs.
This updates the use of the exceptions subclassed from
`QlServerException` when the failure reason is user-caused. This ensures
that a 400-class response is returned, instead of a 500-class one.
Jake Landis
Brian Seeders
Michael Peterson
Abdon Pijpelink
Albert Zaharovits
Mayya Sharipova
David Turner
Anton Dosov
Craig Taverner
Costin Leau
Benjamin Trent
Nik Everett
Ignacio Vera
Liam Thompson
Kostas Krikellas
Luigi Dell'Aquila
István Zoltán Szabó
Chris Hegarty
ShourieG
Johannes Fredén
Marco Liberati
Bogdan Pintea
Volodymyr Krasnikov
Martijn van Groningen
Mark Tozzi
ChrisHegarty
Nicolas Gras
Mary Gouseti