[
https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833649#comment-15833649
]
Elias Levy commented on KAFKA-4144:
-----------------------------------
That's fine. I am less concerned about the implementation details than about
the developer's API experience. E.g. having {{TopologyBuilder.addSource}},
{{KStreamBuilder.source}}, and {{KStreamBuilder.table}} take a
{{TimestampExtractor}}.
There is another problem with {{TimestampExtractor}}. It is instantiated
within StreamTask and the instances cannot be configured. That means that the
topics that {{TimestampExtractor}} supports are hardcoded into it. That makes
it impossible to have a Stream application that uses {{TimestampExtractor}}
were the input topics can be configured at execution time.
> 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)
