[
https://issues.apache.org/jira/browse/SAMZA-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tao Feng updated SAMZA-838:
---------------------------
Description: Samza supports TTL since SAMZA-537 is checked-in. From
https://github.com/facebook/rocksdb/wiki/Time-to-Live, if ttl is negative, ttl
won't happen. But in Samza code base(RocksDbKeyValueStore.scala), if user
specifies negative rocksdb.ttl.ms, Samza will treat it as 1 second ttl. I am
not sure if this is intended or a trivial bug. I could provide a quick fix for
this issue if needed. (was: Samza supports TTL since
https://issues.apache.org/jira/browse/SAMZA-537 is checked-in. From
https://github.com/facebook/rocksdb/wiki/Time-to-Live, if ttl is negative, ttl
won't happen. But in Samza code base(RocksDbKeyValueStore.scala), if user
specifies negative rocksdb.ttl.ms, Samza will treat it as 1 second ttl. I am
not sure if this is intended or a trivial bug. I could provide a quick fix for
this issue if needed.)
> negative rocksdb.ttl.ms does not handle correctly
> --------------------------------------------------
>
> Key: SAMZA-838
> URL: https://issues.apache.org/jira/browse/SAMZA-838
> Project: Samza
> Issue Type: Bug
> Reporter: Tao Feng
> Assignee: Tao Feng
> Priority: Trivial
>
> Samza supports TTL since SAMZA-537 is checked-in. From
> https://github.com/facebook/rocksdb/wiki/Time-to-Live, if ttl is negative,
> ttl won't happen. But in Samza code base(RocksDbKeyValueStore.scala), if user
> specifies negative rocksdb.ttl.ms, Samza will treat it as 1 second ttl. I am
> not sure if this is intended or a trivial bug. I could provide a quick fix
> for this issue if needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
