[
https://issues.apache.org/jira/browse/KAFKA-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269155#comment-15269155
]
Ismael Juma commented on KAFKA-3646:
------------------------------------
Updating this issue with conversation that happened elsewhere. `KafkaProducer`
already does the following:
{code}
long timestamp = record.timestamp() == null ? time.milliseconds() :
record.timestamp();
{code}
Given this, [~guozhang] tried the example using trunk and he was unable to
reproduce the issue. The conversation in the mailing list thread is ongoing to
try and figure out what is the actual issue.
> Console producer using new producer should set timestamp
> --------------------------------------------------------
>
> Key: KAFKA-3646
> URL: https://issues.apache.org/jira/browse/KAFKA-3646
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Fix For: 0.10.0.0
>
>
> {{kafka.tools.ConsoleProducer}}'s default usage of the new producer does not
> explicitly set the timestamp, and hence for default timestamp type settings
> (CreationTime) the returned timestamp from broker would be set to -1.
> We need to consider whether or not it makes sense to set the timestamp in
> console producer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
