Skip to content

Correctly handle nulls in nested paths in the remove processor #126417

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

Merged
merged 7 commits into from
Apr 7, 2025

Conversation

joegallo
Copy link
Contributor

@joegallo joegallo commented Apr 7, 2025

Fixes a bug that was introduced by #125232.

During path traversal, if we find a null, then that doesn't necessarily mean we must throw an exception -- rather, we should only throw an exception on null if ignoreMissing is false.

joegallo added 3 commits April 7, 2025 11:27
If we run into a null, just treat that the same as any other missing
field -- so if ignoreMissing is true, then we should not throw an
exception.
@joegallo joegallo added >bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Team:Data Management Meta label for data/management team v8.19.0 v9.1.0 labels Apr 7, 2025
@joegallo joegallo requested a review from parkertimmins April 7, 2025 15:54
@joegallo joegallo added the auto-backport Automatically create backport pull requests when merged label Apr 7, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@elasticsearchmachine
Copy link
Collaborator

Hi @joegallo, I've created a changelog YAML for you.

@joegallo joegallo requested a review from parkertimmins April 7, 2025 16:38
Copy link
Contributor

@parkertimmins parkertimmins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@joegallo joegallo merged commit bead858 into elastic:main Apr 7, 2025
17 checks passed
@joegallo joegallo deleted the remove-processor-null-in-path branch April 7, 2025 20:54
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.x Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 126417

elasticsearchmachine added a commit that referenced this pull request Apr 8, 2025
…126463)

* Correctly handle nulls in nested paths in the remove processor (#126417)

* [CI] Auto commit changes from spotless

---------

Co-authored-by: elasticsearchmachine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged >bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Team:Data Management Meta label for data/management team v8.19.0 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants