-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[8.18] Update transport version directory structure (#132891) #133002
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
fixed a typo for "jvm.options.d"
…c#128267) * Add NamedWriteable for QueryRule rank doc * Update test * Update docs/changelog/128153.yaml * Add multi cluster test for query rules * Commenting out code - explicitly trying to spur a test failure * [CI] Auto commit changes from spotless * Streamline test for multi cluster * Revert changes to try to break test * Fix compile error --------- Co-authored-by: elasticsearchmachine <[email protected]> (cherry picked from commit b335c1a) # Conflicts: # x-pack/plugin/ent-search/src/yamlRestTest/resources/rest-api-spec/test/entsearch/rules/40_rule_query_search.yml
…#127534) (elastic#128309) Adds the ForkJoinPool.commonPool-worker- prefix to the Thread getName().startsWith() checks in HdfsClientThreadLeakFilter. This resolves the "There are still zombie threads that couldn't be terminated" errors in the Hdfs IT tests. Closes elastic#128305 Closes elastic#128306 Closes elastic#128307 Closes elastic#128308 (cherry picked from commit 4408e38)
…8223) (elastic#128304) (elastic#128313) * Use package to suppress warning for entitlement self-test * [CI] Auto commit changes from spotless --------- Co-authored-by: elasticsearchmachine <[email protected]>
…elastic#128333) * Using correct origin for inference action * Update docs/changelog/128327.yaml * [CI] Auto commit changes from spotless --------- Co-authored-by: elasticsearchmachine <[email protected]> (cherry picked from commit 19e18a9) # Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/inference/InferenceRunner.java
…orks of 1 (elastic#126346) (elastic#128390) (cherry picked from commit a13a46a)
…tudes (elastic#128259) (elastic#128426) (elastic#128427) It turns out in elastic#128234 that Lucene pushdown on ST_DISTANCE with invalid points (latitude out of range) will cause all documents to be returned, since DISJOINT on an invalid circle is true for all documents. We could either add an extra check for spatial pushdown that the geometries are valid, or add validation at geometry creation. This second option is much easier to implement, and a more comprehensive approach, as it prevents invalid geometries in many more places, hopefully reducing the likelihood of subtle and obscure bugs like elastic#128234 happening in future.
Co-authored-by: Brian Seeders <[email protected]>
…8493) * Explains why you must run increasingly large analyses rather than just accepting the first run. * Expands the docs about why failures are bad even if snapshots appear to work. * Mentions verifying the reference implementation before reporting ES bugs. Backport to `8.19` of elastic/elasticsearch-specification#4413
…tic#128350) (elastic#128446) Adding `logs-aws.config-*` data stream indices to the `kibana_system` privileges. This is required for the latest transform to work. Related: - elastic/integrations#13830 (comment) (cherry picked from commit 169527f)
…lastic#128410) When using synthetic source, runtime fields data may come from doc values. Doc values iterators can only be read once, and in increasing docId order. But if a runtime field is referenced multiple times in a query, currently the same doc value iterator will be used. This causes an error, as the second field reference will attempt to read the same iterator from a lower docId than was previously used. The fix is to create a new source loader, and thus a new doc value iterator, if the requested docId is lower than the last seen docId. (cherry picked from commit 51e87cb) # Conflicts: # server/src/main/java/org/elasticsearch/search/lookup/ConcurrentSegmentSourceProvider.java
* Add Connectors release notes for 8.18 * [DOCS]: Add connectors release notes 8.17.x (elastic#128553) * Add Connectors release notes for 8.17.x
Update Gradle wrapper to 8.14.1 (cherry picked from commit 657f5ff) # Conflicts: # build-tools-internal/src/main/resources/minimumGradleVersion
…ments in read-only indices (elastic#125408) (elastic#128749) * [ML] Prevent retention classes from failing when deleting documents in read-only indices (elastic#125408) Classes like UnusedStatsRemover delete orphaned documents without an associated job. When the indices are made read-only it will start failing as read-only means no delete. This PR ensures that the non-writable indices are not included in the delete-by-query requests. (cherry picked from commit c822a57) * [CI] Auto commit changes from spotless * fit build failure --------- Co-authored-by: elasticsearchmachine <[email protected]>
) (elastic#128756) (cherry picked from commit adda402) # Conflicts: # x-pack/plugin/rank-rrf/src/main/java/org/elasticsearch/xpack/rank/RankRRFFeatures.java
…ster name (elastic#128610) (elastic#128843) The auth code injects the pattern `["*", "-*"]` to specify that it's okay to return an empty response because user's patterns did not match any remote clusters. However, we fail to recognise this specific pattern and `groupIndices()` eventually associates it with the local cluster. This causes Elasticsearch to fallback to the local cluster unknowingly and return its details back to the user even though the user hasn't requested any info about the local cluster. (cherry picked from commit 3f1e1b3) # Conflicts: # server/src/main/java/org/elasticsearch/transport/RemoteClusterService.java
…8924) * initial implementation for match_All * reformat * [CI] Auto commit changes from spotless * Excluding matchAllintercepter * Adding matchAllDocs support for vector fields * [CI] Auto commit changes from spotless * Remove previous implementation * Adding yaml tests for match_all * fixed yaml tests * Update docs/changelog/128702.yaml * Update changelog * changelog - update summary * Fix wrong inference names for the yaml tests --------- Co-authored-by: elasticsearchmachine <[email protected]> Co-authored-by: Elastic Machine <[email protected]> (cherry picked from commit d1b5532) # Conflicts: # x-pack/plugin/inference/src/main/java/org/elasticsearch/xpack/inference/InferenceFeatures.java # x-pack/plugin/inference/src/yamlRestTest/resources/rest-api-spec/test/inference/90_semantic_text_highlighter.yml # x-pack/plugin/inference/src/yamlRestTest/resources/rest-api-spec/test/inference/90_semantic_text_highlighter_bwc.yml
…step (elastic#132387) (elastic#132574) * [ExtraHop][Qualys GAV] - Fix Cannot execute ILM policy delete step (elastic#132387) This PR focuses on the short term solution which add the logs-extrahop.investigation-* and logs-qualys_gav.asset-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PRs. (cherry picked from commit 0d7a2cc) * Update KibanaOwnedReservedRoleDescriptors.java added missing imports in KibanaOwnedReservedRoleDescriptors * [CI] Auto commit changes from spotless --------- Co-authored-by: elasticsearchmachine <[email protected]>
…132639) It was removed in 8.0.
…indices to kibana_system role permissions (elastic#132445) (elastic#132630) * Add {m365_defender,microsoft_defender_endpoint}.vulnerability indices to kibana_system role permissions (elastic#132445) Add logs-m365_defender.vulnerability-* and logs-microsoft_defender_endpoint.vulnerability-* data stream indices to the kibana_system's read privileges. This is required for the latest transform for 3rd party integrations CDR workflows (vulnerability findings) to work. Also add delete_index on logs-m365_defender.vulnerability-* and logs-microsoft_defender_endpoint.vulnerability-* to facilitate index removal through ILM policies. (cherry picked from commit 716bff8) # Conflicts: # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authz/store/KibanaOwnedReservedRoleDescriptors.java * fix conflicts * fix conflicts
…lastic#132647) * Add tasks to validate new style transport versions (elastic#131782) This commit adds new gradle plugins and tasks to handle validation of file based transport version definitions. Co-authored-by: Ryan Ernst <[email protected]> Co-authored-by: John Verwolf <[email protected]> * skip if no named constants yet * [CI] Auto commit changes from spotless * temporarily add leniency for definitions dir * [CI] Auto commit changes from spotless --------- Co-authored-by: John Verwolf <[email protected]> Co-authored-by: elasticsearchmachine <[email protected]>
Create docs for Transform's upgrade mode Relate elastic#132510
Co-authored-by: elasticsearchmachine <[email protected]>
…c#132546) (elastic#132692) * [ML] Improve EIS auth call logs and fix revocation bug (elastic#132546) * Fixing revoking and adding logs * Fixing tests * Update docs/changelog/132546.yaml * [CI] Auto commit changes from spotless * Addressing feedback --------- Co-authored-by: elasticsearchmachine <[email protected]> * Fixing mock registry --------- Co-authored-by: elasticsearchmachine <[email protected]>
…lastic#132864) * [Gradle] Update nebula ospackage plugin to 12.1.0 - 12.1.0 is required by Gradle 9.x these days and required before we can update to the newest Gradle version * Fix issue with file permissions in deb and rpm archives * Cleanup dependency metadata
* Forward port release notes for v8.17.10 * Update release-notes.asciidoc --------- Co-authored-by: elasticsearchmachine <[email protected]> Co-authored-by: Charlotte Hoblik <[email protected]>
…#132779) This commit adds additional validation cases to the new transport version resource files. It also adds gradle tests for the validation cases. Co-authored-by: Jack Conradson <[email protected]>
…tic#132694) (elastic#132862) (elastic#132881) This change moves transport version loading out of TransportVersion.VersionsHolder, so that is can be consumed elsewhere by projects using the same resource file structure. Jira: ES-12401
…stic#132887) The utilities class has basically become a package itself. This commit moves inner records from TransportversionUtils and some related functions out to their own files.
…elastic#132882) (elastic#132899) The build system for transport versions operate on two different types of projects. A project can have named references to transport versions, and it could also be the source of truth for transport version resources, where latest and definitions files exist. This commit renames the plugins and tasks to consistently use that terminology.
This changes the directory structure for transport version files to the following: /transport/latest /transport/definitions/named /transport/definitions/initial /transport/definitions/manifest.txt This allows manifest to be placed in a location for named and initial transport versions without adding confusion to latest. ES-12401
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport
:Core/Infra/Transport API
Transport client API
>refactoring
Team:Core/Infra
Meta label for core/infra team
v8.18.6
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: