[
https://issues.apache.org/jira/browse/KAFKA-12766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342337#comment-17342337
]
Bruno Cadonna commented on KAFKA-12766:
---------------------------------------
I have to admit that I blindly followed your comment here:
https://github.com/apache/kafka/pull/10568#discussion_r626058786
I interpreted "disable" as to not offer methods to read and write this option
to users which seems hard to achieve. Now I see, that I misinterpreted.
I am fine with ignoring. In this case, I would even log a warning if users try
to read or write a WAL-related option since it is not obvious that Streams
disables the WAL.
> Consider Disabling WAL-related Options in RocksDB
> -------------------------------------------------
>
> Key: KAFKA-12766
> URL: https://issues.apache.org/jira/browse/KAFKA-12766
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Bruno Cadonna
> Priority: Minor
> Fix For: 3.0.0
>
>
> Streams disables the write-ahead log (WAL) provided by RocksDB since it
> replicates the data in changelog topics. Hence, it does not make much sense
> to set WAL-related configs for RocksDB instances within Streams.
> Streams could:
> - disable WAL-related options
> - ignore WAL-related options
> - throw an exception when a WAL-related option is set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
