Opster kofi paginate changes rebase #123673
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Skip some more union type tests when running against older versions of Elasticsearch because they *now* require `date_nanos` support. Closes elastic#117108
This fixes sorts containing the a `_source` field. It can use the standard encoder for `BytesRef`s. You can't sort *by* a `_source` field, but that doesn't really make sense ayway.
Adds a test that always fails on one of the data nodes and makes sure this comes back as a failure. When we build support for partial results we can use this test to simulate it.
* Esql Enable Date Nanos (elastic#117080) This enables date nanos support as tech preview. Basic operations, like reading values, binary comparisons, and functions that don't care about type should work, but some functions are not yet supported. Most notably, Bucket is not yet supported, although Date_Trunc is and can be used for grouping. See the docs for the full list of limitations. relates to elastic#109352 * Skip CATEGORIZE tests outside snapshot --------- Co-authored-by: Nik Everett <[email protected]>
elastic#117227) (cherry picked from commit ea4b41f)
…17189) (elastic#117260) * Fix deberta tokenizer bug caused by bug in normalizer which caused offesets to be negative * Update docs/changelog/117189.yaml (cherry picked from commit 5500a5e)
Cleans the release notes for ESQL, removing funny prefixes like `ESQL` and `[ESQL]` and `ES|QL`. The new release notes maker will make them without these prefixes via regex duct tape. This cleanes the last release.
…lastic#117288) * Change synthetic source logic for constant_keyword * Update docs/changelog/117182.yaml (cherry picked from commit 3a1bc05)
…astic#117285) ES|QL doesn't work well with 500 clusters or clusters with 500 nodes. The reason is that we enqueue three tasks to the thread pool queue, which has a limit of 1000, during the initialization of the exchange for each target (cluster or node). This simple PR reduces it to one task. I'm considering using AsyncProcessor for these requests, but that will be a follow-up issue for later.
Add documentation for aggs filtering (the WHERE in STATS command). Fixes: elastic#115083
It's not PREVIEW.
We built this a while back. Let's document it.
…astic#117297) (elastic#117388) [esql] > Unexpected error from Elasticsearch: illegal_state_exception - sink exchanger for id [ruxoDDxXTGW55oIPHoCT-g:964613010] already exists. This issue occurs when two or more clusterAliases point to the same physical remote cluster. The exchange service assumes the destination is unique, which is not true in this topology. This PR addresses the problem by appending a suffix using a monotonic increasing number, ensuring that different exchanges are created in such cases. Another issue arising from this behavior is that data on a remote cluster is processed multiple times, leading to incorrect results. I can work on the fix for this once we agree that this is an issue.
elastic#117424) when building nesting bwc distros we tend to generate empty buildkite artifacts. Lets not create empty archives
…ic#117439) Each data-node request involves two exchange sinks: an external one for fetching pages from the coordinator and an internal one for node-level reduction. Currently, the test selects one of these sinks randomly, leading to assertion failures. This update ensures the test consistently selects the external exchange sink. Closes elastic#117397
In the ManyShardsIT#testRejection test, we intercept exchange requests and fail them with EsRejectedExecutionException, verifying that we return a 400 response instead of a 500. The issue with the current test is that if a data-node request never arrives because the whole request was canceled after the exchange request failed—the leftover exchange sink remains until it times out, which defaults to 5 minutes. This change adjusts the test to use a single data node and ensures exchange requests are only failed after the data-node request has arrived. Closes elastic#112406 Closes elastic#112418 Closes elastic#112424
…ic#117347) This PR fixes unintentional licensed feature overlaps for features with the same name but different family fields.
* Add version prefix to Inference Service API path * Update docs/changelog/117366.yaml
This test suite is less generic than its current name suggests. Relates ES-9984
…stic#117022) (elastic#117480) Co-authored-by: Philippus Baalman <[email protected]>
…astic#119516) (elastic#119527) * fix: do not let `_resolve/cluster` hang if remote is unresponsive Previously, `_resolve/cluster` would wait for a response from a remote as part of the connection strategy. If the remote were to be unresponsive, this API would wait until `netty` would terminate the connection with a handshake exception. The threshold for terminating the connection is `10s`. This means that the API would wait for `10s` before determining that the remote is unresponsive. This strategy is now replaced with a fail fast where a response is sent back to the user immediately rather than waiting for a connection termination. * Update docs/changelog/119516.yaml
elastic#119477) (elastic#119482) (cherry picked from commit 577d102)
…tent pt I of ?) (elastic#119016) (elastic#119525) (cherry picked from commit 9862a43)
elastic#119249) (elastic#119492) This ensures we can use gradle configuration cache with elasticsearch serverless build (cherry picked from commit 1d5706e) # Conflicts: # build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/precommit/CheckstylePrecommitPlugin.java
…19587) (elastic#119595) The groovy syntax we use in branchConsistency task was deprecated in gradle 8.12
* Refactor change point detection (elastic#114289) * Move change detection code to separate class * Uniformize ChangeDetector and SkipeAndDipDetector * Separate ChangeDetectorTests and ChangePointAggregatorTests. * Public entrypoint for change point detection * Move p-value computation to ChangeDetector * Move main entrypoint to a separate file * Fix change point detection for uncertain non-stationary distributions. (elastic#119578) * Fix change point detection for uncertain non-stationary distributions. * Replace -1 by ChangeType.NO_CHANGE_POINT
I believe this is a typo, as in our 8.16.1 cluster this field appears to be called `combined_coordinating_and_primary`
…mpat (elastic#119044) (elastic#119664) (cherry picked from commit cc0e53e) # Conflicts: # muted-tests.yml # qa/mixed-cluster/build.gradle
…lastic#119684) - reference a Gradle script object from a Groovy closure during execution phase is not allowed
…c#119637) (elastic#119640) * Fix spike detection for short spikes at the tail of the data. * Update docs/changelog/119637.yaml
…stic#118999) (elastic#119222) * Adding context preserving fix * Update docs/changelog/118999.yaml * Update docs/changelog/118999.yaml * Using a setonce and adding a test * Updating the changelog (cherry picked from commit 7ba3cb9) # Conflicts: # x-pack/plugin/inference/qa/inference-service-tests/src/javaRestTest/java/org/elasticsearch/xpack/inference/InferenceBaseRestTest.java # x-pack/plugin/inference/qa/inference-service-tests/src/javaRestTest/java/org/elasticsearch/xpack/inference/InferenceCrudIT.java # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/InferencePlugin.java # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/rest/RestUnifiedCompletionInferenceAction.java # x-pack/plugin/inference/src/test/java/org/elasticsearch/xpack/inference/rest/RestUnifiedCompletionInferenceActionTests.java
|
Documentation preview: |
elasticsearchmachine
added
v9.1.0
external-contributor
|
Made a mistake in creating this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
61 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Premigration changes made but didn't get merged in time. This is a dupe of #120171