kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elias Levy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4144) Allow per stream/table timestamp extractor
Date Tue, 24 Jan 2017 22:14:26 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836739#comment-15836739
] 

Elias Levy commented on KAFKA-4144:
-----------------------------------

What Matthias said.  The issue has nothing to do with different applications.  The problem
is that the single configurable TimestampExtractor is used for all input topics.  That means
you must dump the timestamps extraction logic for all topics, which may be quite different,
into a single TimestampExtractor.

Imagine if you could only configure a single SerDe that would have to handle all topics, instead
of being able to configure a SerDe per topic.

> 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)

Mime
View raw message