> I have serious concerns regarding reducing the TTL to 15 yrs.The patch will
> immediately break all existing applications in Production which are using 15+
> yrs TTL.
In order to prevent applications from breaking I will update the patch
to automatically set the maximum TTL to '03:14:08 UTC 19
Hi,
the cassandra cpp driver I'm using to connect to a cluster prints the
following warning when I'm creating a keyspace from my application:
1516956724.720 [WARN] (src/token_map.cpp:396:void
cass::ReplicationStrategy::build_replicas_network_topology(const
TokenHostVec&, const cass::DatacenterMap
Hi Jeff,
One correction in my last message: "it may be more feasible to SUPPORT (not
extend) the 20 year limit in Cassandra in 2.1/2.2".
I completely agree that the existing 20 years TTL support is okay for older
versions.
If I have understood your last message correctly, upcoming patches are
If its a 32 bit timestamp, can't we just save/read localDeletionTime as
unsinged int? That would give it another 68 years. I think everyone
involved here could live with that limitation :-)
On Fri, Jan 26, 2018 at 8:16 AM, Anuj Wadehra <
anujw_2...@yahoo.co.in.invalid> wrote:
> Hi Jeff,
>
> Than
