You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2015/12/14 18:41:46 UTC

[jira] [Commented] (SAMZA-838) negative rocksdb.ttl.ms is not handled correctly

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

Yi Pan (Data Infrastructure) commented on SAMZA-838:
----------------------------------------------------

Hi, [~TaoFeng], this seems to be a bug. We should honor the semantic definition rocksdb defines for negative TTL values.

> negative rocksdb.ttl.ms  is not handled 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 . 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 just 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)