[
https://issues.apache.org/jira/browse/CAMEL-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320158#comment-17320158
]
Jens Kordowski commented on CAMEL-16414:
----------------------------------------
I just checked the PR, thanks for providing it. I have an improvement proposal
though. It requires a java.lang.Long as datatype. In a lot of cases headers are
sent as text (String), for instance sending a header via some rest client to a
route. Do you want me to add a new improvement item for this? (I can provide
the PR also myself, just a little short on time currently. Maybe someone picks
it up in the meantime.)
> camel-kafka set custom timestamp
> --------------------------------
>
> Key: CAMEL-16414
> URL: https://issues.apache.org/jira/browse/CAMEL-16414
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Affects Versions: 2.25.3, 3.8.0
> Reporter: Jens Kordowski
> Assignee: Ramu
> Priority: Major
> Fix For: 3.10.0
>
>
> 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?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
