[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-dev
Subject:    Re: Regarding CASSANDRA-14227
From:       Benedict Elliott Smith <benedict () apache ! org>
Date:       2019-01-11 12:43:36
Message-ID: 2BC46895-8863-4963-A651-6064594E9FBE () apache ! org
[Download RAW message or body]

The project is primarily pushing towards a higher quality 4.0 release, so I am \
unaware of anybody considering this bug.

There's a strong argument to be made for this to be fixed in 4.0, since it ideally \
requires a major version bump.  I can't promise anybody will prioritise this over \
their other work for 4.0, though.  I don't believe any active contributors use TTLs \
this large, so it is not so urgent for them.




> On 11 Jan 2019, at 11:01, manish khandelwal <manishkhandelwal03@gmail.com> wrote:
> 
> Hi Team
> 
> We are not able to insert data with large TTLs (expiration time beyond
> 2038-01-19T03:14:06+00:00).
> 
> Even though https://jira.apache.org/jira/browse/CASSANDRA-14092 prevented a
> workaround to avoid data loss, the permanent fix is still pending. I can
> see that the JIRA: https://jira.apache.org/jira/browse/CASSANDRA-14227
> which was open for permanent fix is still in unassigned state. I think it's
> a high priority issue as the timestamp limit is continuously reducing as we
> approach 2038. Are there any plans to prioritize and fix the ticket?
> 
> 
> Regards
> 
> Manish


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


[prev in list] [next in list] [prev in thread] [next in thread]