[
https://issues.apache.org/jira/browse/CAMEL-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramu updated CAMEL-16481:
-------------------------
Description:
Implement CAMEL-16414:camel-kafka set custom timestamp for vertx-kafka
was:
The kafka producer supports the possibility to pass on a (custom) timestamp
with the record. The camel-kafka component does not leverage this, currently. A
Camel header seems like a good option to provide this. The consumer already
creates a kafka.TIMESTAMP header (not yet documented). I suggest to use a
different header to avoid misconfiguration in case of "kafka to kafka"
scenarios. kafka.OVERRIDE_TIMESTAMP (being a one-time header) looks like a good
idea, similar to the existing kafka.OVERRIDE_TOPIC.
What do you think?
> vertx-kafka set custom timestamp
> ---------------------------------
>
> Key: CAMEL-16481
> URL: https://issues.apache.org/jira/browse/CAMEL-16481
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 2.25.3, 3.8.0
> Reporter: Ramu
> Assignee: Ramu
> Priority: Major
> Fix For: 3.10.0
>
>
> Implement CAMEL-16414:camel-kafka set custom timestamp for vertx-kafka
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
