-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[8.18] Refactor transport version constants into new file system (#133849) #134000
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
…lastic#129791) (elastic#129857) We can now run projects check tasks and :distribution:generateDependenciesReport with configuration cache enabled (--configuration-cache)
* Adds Connectors release note for 8.18.3 * Add release note * Updates release notes
Link directly to the Transform reindex migration guide.
elastic#129325) (elastic#129909) (cherry picked from commit 816caf7)
…129960) The comment in `TransportHandshaker` indicates (correctly) that we emit a warning when talking to a chronologically-newer-yet-numerically-older version, but the wording of the warning message is inverted and says that the remote is chronologically-older-yet-numerically-newer. This commit straightens out the message to match the situation it is describing. Relates elastic#123397 Backport of elastic#129904 to `8.19`
* Forward port release notes for v8.17.8 * Forward port release notes for v8.17.7
…lastic#130060) The local plan optimizer should not change the layout, as it has already been agreed upon. However, CombineProjections can violate this when some grouping elements refer to the same attribute. This occurs when ReplaceFieldWithConstantOrNull replaces missing fields with the same reference for a given data type. Closes elastic#128054 Closes elastic#129811 (cherry picked from commit 2bc6284)
…lastic#130096) 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.
…astic#130083) (elastic#130103) 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.
…tic#130106) (cherry picked from commit 21180df) # Conflicts: # x-pack/plugin/inference/build.gradle
…lastic#130121) * Fail startup if entitlement instrumentation failed (elastic#130051) Java class transformers swallow exceptions, so any instrumentation failures, for example due to a java version mismatch, will silently proceed with startup, which then will cryptically fail the entitlement self test. This commit logs exceptions that occur during instrumentation, as well as plumb through the fact that any occured so that bootstrap can fail rather than allow startup to proceed. * [CI] Auto commit changes from spotless --------- Co-authored-by: elasticsearchmachine <[email protected]>
…#130179) (elastic#130197) Maven central expects signed artifacts when publishing (cherry picked from commit 5995602) # Conflicts: # .buildkite/pipelines/dra-workflow.yml
…stic#130245) When the entitelement agent fails to load the underlying exception can be cryptic. In some casees it may be that the path the agent jar is bad. This commit expands the exception message to show the agent path that we tried to load.
…lastic#130229) (elastic#130322) * Manually backport the change * Update docs/reference/connector/docs/connectors-mongodb.asciidoc --------- Co-authored-by: Liam Thompson <[email protected]>
Newlines are system dependent. The release notes generator uses groovy's template engine, which produces system dependent newlines. This commit adjusts the test to account for newlines on both windows and nix systems.
…tic#130412) (elastic#130446) - Ensure we include sources and javadoc jar to maven publication (cherry picked from commit 50d0474)
elastic#130456) * ESQL: Keep `DROP` attributes when resolving field names (elastic#127009) (elastic#128147) (cherry picked from commit 54f2668) Co-authored-by: kanoshiou <[email protected]> * [CI] Auto commit changes from spotless --------- Co-authored-by: kanoshiou <[email protected]> Co-authored-by: elasticsearchmachine <[email protected]>
…ess with that code. (elastic#133688) (elastic#133727) So let's just drop it - if we ever do dare to change the conversion code, we can add proper tests then. (cherry picked from commit 50c3cd4) # Conflicts: # muted-tests.yml # server/src/test/java/org/elasticsearch/index/mapper/LongFieldMapperTests.java
…33740) Most upper bounds files for transport version are for an already branched version. For those, the upper bound must be within the base id for that branch, and validation exists to ensure the highest id within a branch is in the upper bound file for that branch. But for main the base is always different. This commit adds validation to ensure that the highest transport version id exists in _some_ upper bound file. Note that while we could try to identify which upper bound file belongs to main, this is tricky when validation runs in non-main branches. This check is just as good, just a little less specific than "it should exist in x.y upper bound file".
…#133751) (elastic#133756) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
…tic#133567) * [Gradle] Avoid usage of archives configuration This will be deprecated in later Gradle versions * Remove unused wiring in distribution project * minor tweak
… for transform (elastic#133623) (elastic#133800) Add logs-microsoft_defender_cloud.assessment data stream indices to the kibana_system's read privileges. This is required for the latest transform for 3rd party integrations CDR workflows (vulnerability and misconfigurations findings) to work. Also adds delete_index on logs-microsoft_defender_cloud.assessment-* to facilitate index removal through ILM policies. Related: For elastic/integrations#14785 Similar to elastic#132445 (cherry picked from commit eb005b0)
…ic#133795) (elastic#133802) This increases the test suite timeout for CcsCommonYamlTestSuiteIT from 15 to 20 minutes and for RcsCcsCommonYamlTestSuiteIT from 20 to 25 minutes. This is currently necessary because the suite frequently time out in encryption-at-rest builds. Relates to elastic#133409
…lastic#133787) (cherry picked from commit 4a745b5) # Conflicts: # muted-tests.yml
An exception here should be impossible, but we don't assert that, nor do we emit a log message to prove it didn't happen in a production environment. This commit adds the missing log and assert. Backport of elastic#131418 to `8.18`
) (elastic#133910) * Check entitlements for URLClassLoader.newInstance (elastic#132725) * fix backport
…stic#133933) Co-authored-by: Rassyan <[email protected]>
… (elastic#133950) This PR bumps the remaining usage of old asm versions to 9.8 for support of JDK 25. Relates to ES-12644
…lastic#133476) Gradle task added to modify `branches.json`. Possibility to add, remove and update branches in the file with the version field added next to the branch. BwC test configuration has been changed to use changed `branches.json` file to calculate unreleased ES versions, instead of combining data from `Version.java` and `branches.json`.
…3849) This refactors ZERO, MINIMUM_COMPATIBLE, and MINIMUM_CCS_VERSION into TransportVersion.VersionsHolder and load them from /transport/constants/....
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-merge-without-approval
Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!)
backport
:Core/Infra/Transport API
Transport client API
>refactoring
Team:Core/Infra
Meta label for core/infra team
v8.18.7
v9.2.0
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.
Backports the following commits to 8.18: