-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
[Profiling] Fix NullPointerExceptions by accepting dotted field names #124506
Merged
rockdaboot
merged 2 commits into
elastic:main
from
rockdaboot:profiling-fix-dotted-fields
Mar 12, 2025
Merged
[Profiling] Fix NullPointerExceptions by accepting dotted field names #124506
rockdaboot
merged 2 commits into
elastic:main
from
rockdaboot:profiling-fix-dotted-fields
Mar 12, 2025
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
Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
christos68k
approved these changes
Mar 10, 2025
rockdaboot
added a commit
to rockdaboot/elasticsearch
that referenced
this pull request
Mar 12, 2025
…elastic#124506) * [Profiling] Fix NullPointerExceptions by accepting dotted field names Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co> * Evaluate source only once (cleanup) --------- Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
rockdaboot
added a commit
to rockdaboot/elasticsearch
that referenced
this pull request
Mar 12, 2025
…elastic#124506) * [Profiling] Fix NullPointerExceptions by accepting dotted field names Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co> * Evaluate source only once (cleanup) --------- Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
rockdaboot
added a commit
to rockdaboot/elasticsearch
that referenced
this pull request
Mar 12, 2025
…elastic#124506) * [Profiling] Fix NullPointerExceptions by accepting dotted field names Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co> * Evaluate source only once (cleanup) --------- Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
rockdaboot
added a commit
that referenced
this pull request
Mar 12, 2025
…#124506) (#124621) * [Profiling] Fix NullPointerExceptions by accepting dotted field names Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. * Evaluate source only once (cleanup) --------- Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
rockdaboot
added a commit
that referenced
this pull request
Mar 12, 2025
…#124506) (#124622) * [Profiling] Fix NullPointerExceptions by accepting dotted field names Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. * Evaluate source only once (cleanup) --------- Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
rockdaboot
added a commit
that referenced
this pull request
Mar 12, 2025
…#124506) (#124623) * [Profiling] Fix NullPointerExceptions by accepting dotted field names Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. * Evaluate source only once (cleanup) --------- Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
rockdaboot
added a commit
that referenced
this pull request
Mar 12, 2025
…#124506) (#124624) * [Profiling] Fix NullPointerExceptions by accepting dotted field names Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. * Evaluate source only once (cleanup) --------- Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
albertzaharovits
pushed a commit
to albertzaharovits/elasticsearch
that referenced
this pull request
Mar 13, 2025
…elastic#124506) * [Profiling] Fix NullPointerExceptions by accepting dotted field names Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co> * Evaluate source only once (cleanup) --------- Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
jfreden
pushed a commit
to jfreden/elasticsearch
that referenced
this pull request
Mar 13, 2025
…elastic#124506) * [Profiling] Fix NullPointerExceptions by accepting dotted field names Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found. This PR fixes the NullPointerExceptions that could happen with dotted field names. Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co> * Evaluate source only once (cleanup) --------- Signed-off-by: Tim Rühsen <tim.ruhsen@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
external-contributor
Pull request authored by a developer outside the Elasticsearch team
Team:obs-ux-infra_services
Observability Infrastructure & Services User Experience Team
:UniversalProfiling/Application
Elastic Universal Profiling REST APIs and infrastructure
v8.17.4
v8.18.0
v8.19.0
v9.0.0
v9.1.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.
Profiling uses synthetic source and thus expects nested field names in query responses. With 8.17+, synthetic source is available only to Enterprise (or higher) subscriptions, so that smaller subscriptions have dotted field names in query responses. The profiling plugin relies on nested field names and runs into NullPointerExceptions if these are not found.
This PR fixes the NullPointerExceptions that could happen with dotted field names.