[8.x][Entitlements] Fix "No SecurityManager when entitlements are enabled" #119764
Conversation
This file contains 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
) (elastic#118836) We do not have SearchStats for fields from lookup indices. And unfortunately, these are hard to obtain. For now, just do not apply ReplaceMissingFieldWithNull to fields coming from an index used in LOOKUP JOIN. These are identified via their indexmode.
Add section about removing index Co-authored-by: Adam Szaraniec <[email protected]>
…#118862) Allow queries to succeed if some shards are failing
Remove "coming" tags
Remove "coming" tags
…0_metrics_ingest/Test metrics-apm.app-* setting event.ingested via ingest pipeline} elastic#118875
…ic#118879) We are changing the format of an unreleased API in elastic#118803. This causes yamlRestCompatTest to fail. This PR is commenting out the failed test for now. Once elastic#118803 goes in, I'll backport the change and reenable this test (with the new structure).
…)" (elastic#118609)" (elastic#118880) (elastic#118883) This reverts commit 7662b78.
…st {p0=synonyms/90_synonyms_reloading_for_synset/Reload analyzers for specific synonym set} elastic#116777
…lastic#118744) (elastic#118884) * [8.x] Add min. read-only index version compatible to DiscoveryNode (elastic#118744) In a short future we'd like to use this information in methods like IndexMetadataVerifier#checkSupportedVersion and NodeJoineExecutor to allow opening indices in N-2 versions as read-only indices on ES V9. * MINIMUM_READONLY_COMPATIBLE
… (elastic#118885) This PR enables the resolution of field names containing "." after the rollover of the anomalies results index. This way, the object parts of the field name, e.g., for an influencer, will indeed have the object type and can be resolved in search and filter operations.
…lastic#118674) (elastic#118886) In anomaly detection, score renormalization will update the anomaly score in the result indices. However, if the index in the old format was marked as read-only, the score update will fail. Since this failure is expected, this PR suppresses the error logging in this specific case.
resolves elastic#118476 This adds an implicit cast from string to date nanos, much the same as we do for millisecond dates. In the course of working on this, I found and fixed a couple of tests that were creating pre-epoch date nanos, which are not supported in elasticsearch. I also refactored the conversion code to use the standard DateUtils functions where appropriate, which caught some of the above errors in test data.
```
- class: org.elasticsearch.xpack.application.OpenAiServiceUpgradeIT
method: testOpenAiEmbeddings {upgradedNodes=1}
issue: elastic#118156
- class: org.elasticsearch.xpack.application.HuggingFaceServiceUpgradeIT
method: testHFEmbeddings {upgradedNodes=1}
issue: elastic#118197
- class: org.elasticsearch.xpack.application.OpenAiServiceUpgradeIT
method: testOpenAiCompletions {upgradedNodes=2}
issue: elastic#118163
- class: org.elasticsearch.xpack.application.OpenAiServiceUpgradeIT
method: testOpenAiCompletions {upgradedNodes=1}
issue: elastic#118162
- class: org.elasticsearch.xpack.application.HuggingFaceServiceUpgradeIT
method: testElser {upgradedNodes=1}
issue: elastic#118127
- class: org.elasticsearch.xpack.application.CohereServiceUpgradeIT
method: testCohereEmbeddings {upgradedNodes=1}
issue: elastic#116974
```
…tic#118892) Updating with changes in elastic#115041
…t-only (elastic#118853) * Mark the lookup join tests in IndexResolverFieldNamesTests as snapshot-only (elastic#118815) (cherry picked from commit e0763c2) * Unmute the sql test
This PR updates the Elasticsearch ILM tutorial for the newer screenshot and the primary shard update in the text. Co-authored-by: Satyam Mishra <[email protected]>
…o bfdeddb (elastic#118869) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
…lastic#118544) (elastic#118918) (cherry picked from commit 3f1fed0) # Conflicts: # x-pack/plugin/esql/src/test/java/org/elasticsearch/xpack/esql/optimizer/LocalPhysicalPlanOptimizerTests.java
… time (elastic#118925) Closes elastic#116777 This test failed on 8.x due to the inability to merge the backport for elastic#118691 in 8.17 (elastic#118818) as it was blocked by an unrelated test failure.
This change replaces the build with scope parameter in order to make it cleaner when parameter is build and how it is used. (cherry picked from commit b8f4677)
…astic#118854) (elastic#118928) * Make ES|QL scoring tests running consistently in serverless (elastic#118854) * make scoring tests running consistently in serverless enforce _id in books dataset to make doc distribution across shards consistent. books settings with 3 shards to accomodate serverless settings. unmuting scoring tests. scoring test fixed. (cherry picked from commit 140beb1)
…ed when entitlements are enabled (elastic#119689)" This reverts commit e4a4eb1.
…19690) (elastic#119695) This change fixes the store option of the underlying sparse vector field for semantic text. For legacy indices, the store option should remain false since changing this option on an existing index is not allowed and that term vectors are already stored in _source.
…lastic#119738) * Add missing parameter to xpack.info rest-api-spec * Update docs/changelog/118954.yaml
…entitlements are enabled (elastic#119689) (elastic#119741)
(cherry picked from commit afda404)
… {cluster=UPGRADED} elastic#119259
…AccountApiKey {cluster=UPGRADED} elastic#119435
…yNativeRealm {cluster=UPGRADED} elastic#119423
…oc {cluster=UPGRADED} elastic#119434
ldematte
added
>non-issue
:Core/Infra/Core
|
Documentation preview: |
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
ldematte
deleted the
backport/8.x/entitlements/boostrap-disallow-sm-miss
branch
ldematte
restored the
backport/8.x/entitlements/boostrap-disallow-sm-miss
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #119742