Skip to content
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

[Transform] Handle bulk indexing errors due to mapping conflicts #50122

Closed
hendrikmuhs opened this issue Dec 12, 2019 · 1 comment · Fixed by #51307
Closed

[Transform] Handle bulk indexing errors due to mapping conflicts #50122

hendrikmuhs opened this issue Dec 12, 2019 · 1 comment · Fixed by #51307

Comments

@hendrikmuhs
Copy link

If a transform runs into a bulk indexing failure it handles the failure as non-persistent except for:

Mapping conflicts should be added to these checks.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml/Transform)

hendrikmuhs pushed a commit to hendrikmuhs/elasticsearch that referenced this issue Jan 22, 2020
hendrikmuhs pushed a commit that referenced this issue Jan 23, 2020
check bulk indexing error for permanent problems and ensure the state goes into failed instead of
retry. Corrects the stats API to show the real error and avoids excessive audit logging.

fixes #50122
hendrikmuhs pushed a commit that referenced this issue Jan 23, 2020
check bulk indexing error for permanent problems and ensure the state goes into failed instead of
retry. Corrects the stats API to show the real error and avoids excessive audit logging.

fixes #50122
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants