[
https://issues.apache.org/jira/browse/KAFKA-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266129#comment-15266129
]
Michael Noll commented on KAFKA-3646:
-------------------------------------
We should also think about whether a negative timestamp (-1) could cause any
downstream collateral damage in Kafka Streams.
AFAIK we do not yet enforce positive (>=0 or >0) timestamps as such, but for
e.g. UnlimitedWindows we already do enforce that windows may not be configured
with a negative start timestamp (cf. "startOn"):
https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/kstream/UnlimitedWindows.java#L38-L40
> 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)
