From 8f675eae17427f2c8bfa5ca563ba89fa4b29ad80 Mon Sep 17 00:00:00 2001 From: aharrington Date: Wed, 27 Dec 2017 09:57:17 -0700 Subject: [PATCH] correct 'nog' to 'not' --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 340d8474..0b543efa 100644 --- a/README.md +++ b/README.md @@ -133,7 +133,7 @@ See the XML `` example above for a discussion of available `Args` o ### Handling errors -From version 5.5 you have the option to specify how to handle issues with Elasticsearch. Since the sink delivers in a batch, it might be possible that one or more events could actually nog be stored in the Elasticseach store. +From version 5.5 you have the option to specify how to handle issues with Elasticsearch. Since the sink delivers in a batch, it might be possible that one or more events could actually not be stored in the Elasticseach store. Can be a mapping issue for example. It is hard to find out what happened here. There is a new option called *EmitEventFailure* which is an enum (flagged) with the following options: - WriteToSelfLog, the default option in which the errors are written to the SelfLog.