[jira] [Resolved] (SAMZA-1929) Automatically adjust changelog topic level settings, when RocksDB TTL is set

["Wei Song (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SAMZA-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei Song resolved SAMZA-1929.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 1.0

Issue resolved by pull request 682
[https://github.com/apache/samza/pull/682]

> Automatically adjust changelog topic level settings, when RocksDB TTL is set
> ----------------------------------------------------------------------------
>
>                 Key: SAMZA-1929
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1929
>             Project: Samza
>          Issue Type: New Feature
>          Components: kv-store
>            Reporter: Wei Song
>            Assignee: Wei Song
>            Priority: Major
>             Fix For: 1.0
>
>
> When TTL is set on RocksDB, the default usage of log compacted topic for changelog isn't appropriate. Ideally, it should match the behavior with a TTL.
> So we would adjust changelog topic setting, when
>  1) TTL is set for RocksDB and
>  2) Changelog is enabled
>  3) User has not set them
> And we would
>  1) Disable log compaction on Kafka changelog topic
>  2) Set topic TTL to be slightly larger than RocksDB TTL
> User should be able to override this behavior through TableDescriptor.withConfig()
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)