[
https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836638#comment-15836638
]
Matthias J. Sax commented on KAFKA-4144:
----------------------------------------
[~jeyhunkarimov] I don't understand this: "the {{configurations}} are global to
all stream applications" -- usually, each application has a different
configuration. Or do you mean application *instances* (ie, starting the same
application multiple times) -- for this, all instances usually have the same
configuration. But this does not relate to the discussion, because all
instances would set the same timestamp extractor for a source (it would be
wrong to set different timestamp extractors for different instances).
The idea of this JIRA is to enhance the API to allow a {{TimestampExtractor}}
per source operator is to overwrite the config provided default 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)
