[jira] [Updated] (CASSANALYTICS-122) Use long for absolute times and support C* 5.0 extended localDeletionTime

["Yifan Cai (Jira)" <ji...@apache.org>]

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

Yifan Cai updated CASSANALYTICS-122:
------------------------------------
    Summary: Use long for absolute times and support C* 5.0 extended localDeletionTime  (was: Support extended deletion times and also handle Year 2038 problem)

> Use long for absolute times and support C* 5.0 extended localDeletionTime
> -------------------------------------------------------------------------
>
>                 Key: CASSANALYTICS-122
>                 URL: https://issues.apache.org/jira/browse/CASSANALYTICS-122
>             Project: Apache Cassandra Analytics
>          Issue Type: Improvement
>          Components: CDC
>            Reporter: Shailaja Koppu
>            Assignee: Shailaja Koppu
>            Priority: Normal
>          Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> * C* 5.0 extended local deletion time value, using uint for storage and providing APIs and serializations to convert uint to long. Also providing Cell.deletionTimeLongToUnsignedInteger to set deletion time value. C* analytics need to handle these changes to support C* 5.0
>  * There are variables holding absolute times(examples: nowInSeconds, expirationTimeInSec, referenceEpoch and referenceEpochInSeconds, deletionTime), which are currently integers and will go negative after 2038 (Year 2038 problem). C* analytics need to use long for these.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org