-
Notifications
You must be signed in to change notification settings - Fork 25.6k
EnrichProcessorFactory should not throw NPE if missing metadata #55977
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
Conversation
In some cases the Enrich processor factory may be called before it is ready to create processors. While these calls are usually made in error, the response from the Enrich processor is an NPE which is almost always an unhelpful error when debugging an issue.
|
Pinging @elastic/es-core-features (:Core/Features/Ingest) |
mayya-sharipova
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jbaiera
martijnvg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I also encountered problems with the hash processor due to the same erroneous calls to its processor factory. I think we should address that so I opened #56019 for it. |
|
@elasticmachine run elasticsearch-ci/1 |
…tic#55977) In some cases the Enrich processor factory may be called before it is ready to create processors. While these calls are usually made in error, the response from the Enrich processor is an NPE which is almost always an unhelpful error when debugging an issue.
…tic#55977) In some cases the Enrich processor factory may be called before it is ready to create processors. While these calls are usually made in error, the response from the Enrich processor is an NPE which is almost always an unhelpful error when debugging an issue.
…) (#56793) In some cases the Enrich processor factory may be called before it is ready to create processors. While these calls are usually made in error, the response from the Enrich processor is an NPE which is almost always an unhelpful error when debugging an issue.
…) (#56798) In some cases the Enrich processor factory may be called before it is ready to create processors. While these calls are usually made in error, the response from the Enrich processor is an NPE which is almost always an unhelpful error when debugging an issue.
…tic#55977) In some cases the Enrich processor factory may be called before it is ready to create processors. While these calls are usually made in error, the response from the Enrich processor is an NPE which is almost always an unhelpful error when debugging an issue.
…) (#56843) In some cases the Enrich processor factory may be called before it is ready to create processors. While these calls are usually made in error, the response from the Enrich processor is an NPE which is almost always an unhelpful error when debugging an issue.
In some cases the Enrich processor factory may be called before it is
ready to create processors. While these calls are usually made in error,
the response from the Enrich processor is an NPE which is almost always
an unhelpful error when debugging an issue.