raise error when using tracking_field and search_api is not "search_after" #240
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug Report Summary
When using tracking_field with logstash-input-elasticsearch and the default scroll API, Logstash sends the literal string :last_value instead of the resolved timestamp. This causes Elasticsearch to fail parsing with:
Workaround
Use search_api => "search_after" instead of the default scroll.
System has to notify about it somehow. I've spent a lot of time while i figured it out.