Skip to content

Conversation

@jbaiera
Copy link
Member

@jbaiera jbaiera commented Apr 29, 2020

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.
@jbaiera jbaiera added >bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP labels Apr 29, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Ingest)

@elasticmachine elasticmachine added the Team:Data Management Meta label for data/management team label Apr 29, 2020
Copy link
Contributor

@mayya-sharipova mayya-sharipova left a comment

Choose a reason for hiding this comment

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

Thanks @jbaiera

Copy link
Member

@martijnvg martijnvg left a comment

Choose a reason for hiding this comment

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

LGTM

@danhermann
Copy link
Contributor

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.

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.

@jbaiera
Copy link
Member Author

jbaiera commented May 8, 2020

@elasticmachine run elasticsearch-ci/1

@jbaiera jbaiera merged commit b8801a4 into elastic:master May 14, 2020
@jbaiera jbaiera deleted the fix-enrich-factory-npe branch May 14, 2020 19:56
jbaiera added a commit to jbaiera/elasticsearch that referenced this pull request May 14, 2020
…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.
jbaiera added a commit to jbaiera/elasticsearch that referenced this pull request May 14, 2020
…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.
jbaiera added a commit that referenced this pull request May 15, 2020
…) (#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.
jbaiera added a commit that referenced this pull request May 15, 2020
…) (#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.
jbaiera added a commit to jbaiera/elasticsearch that referenced this pull request May 15, 2020
…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.
jbaiera added a commit that referenced this pull request May 19, 2020
…) (#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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Team:Data Management Meta label for data/management team v7.7.1 v7.8.0 v7.9.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants