[
https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833131#comment-15833131
]
Jeyhun Karimov edited comment on KAFKA-4144 at 1/22/17 3:05 PM:
----------------------------------------------------------------
[~elevy] After checking the code, I think we should add extra {{
timestampextractor }} field to {{ SourceNode }} class. In this case there will
be one {{ timeStampExtractor }} per topic partition. As a result, in {{
StreamTask}} constructor, we can get access to particular {{ SourceNode }}'s {{
timeStampExtractor }}. Please let me know your comments on this approach.
was (Author: jeyhunkarimov):
[~elevy] Shouldn't it be per partitioned stream/table? So, we can define
'TimestampExtractor' per application, per stream/table and per partitioned
stream/table ('KGoupedStream', 'KGoupedTable') and the latter would override
the former.
> 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)
