[
https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836328#comment-15836328
]
Jeyhun Karimov edited comment on KAFKA-4144 at 1/24/17 8:58 PM:
----------------------------------------------------------------
[~mjsax] [~elevy] Thanks for your explanation. So basically, if I want to
launch a new stream application and pass {{TimestampExtractor}} to it, I have
to use the {{TimestampExtractor}} which other stream applications are using.
Because, the {{configurations}} are global to all stream applications,
basically I cannot define a new {{TimestampExtractor}} while other applications
are running. Therefore, we want to pass {{TimestampExtractor}} not via
{{configuration}} but with {{TopologyBuilder}} class.
Please correct me if I am wrong.
was (Author: jeyhunkarimov):
[~mjsax] [~elevy] Thanks for your explanation. So basically, if I want to
launch a new stream application and pass {{TimestampExtractor}} to it, I have
to use the {{TimestampExtractor}} which other stream applications are using.
Because, the {{configuration}}s are global to all stream applications,
basically I cannot define a new {{TimestampExtractor}} while other applications
are running. Therefore, we want to pass {{TimestampExtractor}} not via
{{configuration}} but with {{TopologyBuilder}} class.
Please correct me if I am wrong.
> 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)
