[
https://issues.apache.org/jira/browse/CAMEL-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320622#comment-17320622
]
Ramu commented on CAMEL-16414:
------------------------------
[~jenskordowski] we have discussed accepting date in String format. But
kafkaProducer class accepts time in Long format.
so we have to do lot of transformations depending on the input time format.
There are lot of time formats we can set in String and it does eventually adds
complexity at camel-kafka side.
Please raise a new Jira with the Improvement to provide time as string format.
In this case camel-kafka should have a utility/helper method to convert string
date format to Long format . Helper method should accept all existing time
formats and have a logic to convert to Long
Coming to other question ,if any jira in un assigned state. any body can own
and work. if you want to work on jira own
and change to inprogress.
If you can not own jira,then at least update the jira saying working on the
jira so that others know some body is already working
> 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)
