[
https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833899#comment-15833899
]
Matthias J. Sax commented on KAFKA-4144:
----------------------------------------
Some of my thoughts:
1. I don't think, we should have a timestamp extractor per partition. A topic
is a logical unit and should contain similar data in all partitions -- if, the
semantics of the data in a topic should be independent of the number of
partitions.
2. I am not sure about configuring a {{TimestampExtractor}} -- this would not
help with dynamic topic as a configuration step would only happen once at
startup.
3. I am also not sure about putting a {{Map}} of extractors. If you subscribe
to multiple topics together, this indicates that those topics are "similar" and
a single timestamp extractor should be used -- if you need different timestamp
extractors, you just can subscribe to each topic separately.
Also keep in mind, that you can subscribe to topics by pattern -- and all
topics matching the pattern should use the same timestamp extractor.
> Allow per stream/table timestamp extractor
> ------------------------------------------
>
> Key: KAFKA-4144
> URL: https://issues.apache.org/jira/browse/KAFKA-4144
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 0.10.0.1
> Reporter: Elias Levy
> Assignee: Jeyhun Karimov
> Labels: api
>
> At the moment the timestamp extractor is configured via a StreamConfig value
> to KafkaStreams. That means you can only have a single timestamp extractor
> per app, even though you may be joining multiple streams/tables that require
> different timestamp extraction methods.
> You should be able to specify a timestamp extractor via
> KStreamBuilder.stream/table, just like you can specify key and value serdes
> that override the StreamConfig defaults.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
