Add Support for Key TTL Setting for Sink Connector #51
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.
This PR adds support for setting TTL values into Redis keys, either at a record level or via configuration. If set at a record level, this means Kafka producers or SMT processors can be used to set the value
redis.key.ttl
on a per-record basis. Otherwise, users can also specify this property via connector configuration, in which the value will be set to any record written into Redis. If both record-level and configuration-level values are set, then record-level takes precedence.This PR also upgrades the Docker Compose file with newer versions of Kafka, health checks for containers, and an updated Dockerfile to build Kafka Connect.