This allows configuration to have a `-1` dim to read files that have the
`dim` in the file.
Additionally, allows setting numQuerys to `0` to skip the search phase
easily.
This brings in the fixes from #130020, with minor fixes to address review
nits from that PR.
Co-authored-by: Martijn van Groningen <martijn.v.groningen@gmail.com>
With the rise of larger CPU count nodes our current write queue size
might be too conservative. Indexing pressure will still provide protect
against out of memories.
This fixes a race condition in the test scenario, between the merge
scheduler closing and the merge task being scheduled to run. The test
scenario expects that the merge task runs when the scheduler is closed.
If the merge scheduler is closed before the merge task is scheduled, the
merge task will instead be scheduled as aborted.
Fixes: https://github.com/elastic/elasticsearch/issues/125236
* Use `throwInvalidIndexNameException()` to throw invalid ex after
dropping asterisk in `IdentifierBuilder#resolveAndValidateIndex()`
* Assert the message in test
* Refactor
* drop invalid chars from assertion string due to randomisation issue
* Re-assert invalid chars
* Update docs/changelog/130027.yaml
* Update semantic text docs to suggest using index options for customization
* Correct type of index_options
* Move example
* PR feedback
* Copy warning fix
* Specific idx in testMultipleBatchesWithLookupJoin
Do not use `from *` in the test, be more specifc - otherwise other tests
can affect the output if they leave indices behind, affecting the column
count.
* Remove column count validation
That doesn't really tell us much in this test, anyway.
Decreases the periodicity (from 5s to 100ms), for some tests, with which merge tasks are checked if there's sufficient available disk space to execute or if they've been aborted since enqueued for execution.
Fixes#130044
Prepares the `main` branch for the backport of #125631. Specifically,
this adds the version constant for 8.19 to main and the serialization
code that lets main talk to 8.19.
There was a bug in the code for deleting unused and orphan ML data. When deletion using DBQ occurred, the bug caused the request to time out. This PR resolves the issue.
The test method needs to distinguish between the available disk space update values, when they are coming from either FS.
So the update values from the 2 FSs mustn't be equal.
Fixes#129149
Previously BRANCH was used in all cases, but if there is a newer version of the dependency, the incorrect version could be used. BRANCH is still used for snapshot DRA builds because full version is not available in artifacts-snapshot API.
Additionally, added log what URL is used to fetch manifest and make the curl command fail in case of error like 404 response.
