You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "John Roesler (JIRA)" <ji...@apache.org> on 2019/03/22 15:20:00 UTC
[jira] [Commented] (KAFKA-8147) Add changelog topic configuration
to KTable suppress
[ https://issues.apache.org/jira/browse/KAFKA-8147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799102#comment-16799102 ]
John Roesler commented on KAFKA-8147:
-------------------------------------
Hi [~mjduijn],
Thanks for this idea!
This would need a quick KIP, but I don't think it would be too controversial. If you're interested in working on this, I'd be happy to provide whatever assistance/guidance you need. In that case, I think we have time to get it in to 2.3.
Offhand, it seems like we should add `withLoggingEnabled/Disabled` to BufferConfig, but we could explore alternatives in the KIP thread.
Related, while working on KAFKA-7224, I've started to think we may want to be able to configure the bytes store as well, so it's possibly a good idea to design the logging feature with this in mind as well.
Let me know your thoughts!
Thanks again,
John
> Add changelog topic configuration to KTable suppress
> ----------------------------------------------------
>
> Key: KAFKA-8147
> URL: https://issues.apache.org/jira/browse/KAFKA-8147
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 2.1.1
> Reporter: Maarten
> Priority: Minor
> Labels: needs-kip
>
> The streams DSL does not provide a way to configure the changelog topic created by KTable.suppress.
> From the perspective of an external user this could be implemented similar to the configuration of aggregate + materialized, i.e.,
> {code:java}
> changelogTopicConfigs = // Configs
> materialized = Materialized.as(..).withLoggingEnabled(changelogTopicConfigs)
> ..
> KGroupedStream.aggregate(..,materialized)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)