Convert org.apache.kafka.connect.data.Date to epoch millis before sending to Elasticsearch #842
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.
Problem
Lets consider the following kafka schema:
And the target index field:
Currently the date type (org.apache.kafka.connect.data.Date) is being converted to int (epoch days) and ends up in Elasticsearch being interpreted as epoch millis turning it into some datetime long in the past.
Elasticsearch does not suport epoch days type for
date
fields.Solution
Assuming the field is properly indexed as
date
we should pass some of default supported formats likeepoch_millis
.Does this solution apply anywhere else?
If yes, where?
Test Strategy
Testing done:
Release Plan
Bugfix, it might be have some incompatibles with existing user workarounds though.