[
https://issues.apache.org/jira/browse/KAFKA-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15736779#comment-15736779
]
ASF GitHub Bot commented on KAFKA-4393:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/2117
> Improve invalid/negative TS handling
> ------------------------------------
>
> Key: KAFKA-4393
> URL: https://issues.apache.org/jira/browse/KAFKA-4393
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Fix For: 0.10.2.0
>
>
> Currently, Kafka Streams does not handle invalid/negative timestamps returned
> from the {{TimestampExtractor}} gracefully, but fails with an exception,
> because negative timestamps cannot get handled in a meaningful way for any
> time based (ie, window) operators like window aggregates and joins.
> We want to change Streams to a auto-drop behavior for negative timestamps for
> those records (without any further user notification about dropped record) to
> enable users to "step over" those records and keep going (instead of an
> exception). To guard the user from silently dropping messages by default (and
> kept current fail-fast behavior), we change the default extractor
> {{ConsumerRecordTimestampExtractor}} to check the extracted meta-data record
> timestamp and raise an exception if it is negative. Furthermore, we add a
> "drop-and-log" extractor, as this seems to be a common behavior user might
> want to have. For any other behavior, users can still provide a custom
> TS-Extractor implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
