Re: Regarding CASSANDRA-14227
Hi Benjamin, thanks for your response. And Berenguer Blasi you are the shining light for us. Regards Manish On Tue, Feb 21, 2023 at 3:04 PM Berenguer Blasi wrote: > I'm actively working on it :-) > On 21/2/23 9:56, Benjamin Lerer wrote: > > Hi Manish, > It is unfortunately not an easy bug to fix as it has some significant > impact at different levels of the code base. > The plan is to have the fix as part of 5.0 which should be released later > this year. > > Le mar. 21 févr. 2023 à 09:48, manish khandelwal < > manishkhandelwa...@gmail.com> a écrit : > >> Hi Team >> >> We are hit by this bug as we approach the deadline as we reach close to >> 2038 as we can see some of our projects breaching the deadline fixed. >> I can see some progress made in this bug by Berenguer Blasi in last few >> months. I do understand that review timings and development can not be >> predicted but it would be helpful in planning and updating our projects >> with some tentative dates/release when this bug can be targeted. >> >> I would appreciate any indication from community on this. >> >> Regards >> Manish >> >
Re: Regarding CASSANDRA-14227
I'm actively working on it :-) On 21/2/23 9:56, Benjamin Lerer wrote: Hi Manish, It is unfortunately not an easy bug to fix as it has some significant impact at different levels of the code base. The plan is to have the fix as part of 5.0 which should be released later this year. Le mar. 21 févr. 2023 à 09:48, manish khandelwal a écrit : Hi Team We are hit by this bug as we approach the deadline as we reach close to 2038 as we can see some of our projects breaching the deadline fixed. I can see some progress made in this bug by Berenguer Blasi in last few months. I do understand that review timings and development can not be predicted but it would be helpful in planning and updating our projects with some tentative dates/release when this bug can be targeted. I would appreciate any indication from community on this. Regards Manish
Re: Regarding CASSANDRA-14227
Hi Manish, It is unfortunately not an easy bug to fix as it has some significant impact at different levels of the code base. The plan is to have the fix as part of 5.0 which should be released later this year. Le mar. 21 févr. 2023 à 09:48, manish khandelwal < manishkhandelwa...@gmail.com> a écrit : > Hi Team > > We are hit by this bug as we approach the deadline as we reach close to > 2038 as we can see some of our projects breaching the deadline fixed. > I can see some progress made in this bug by Berenguer Blasi in last few > months. I do understand that review timings and development can not be > predicted but it would be helpful in planning and updating our projects > with some tentative dates/release when this bug can be targeted. > > I would appreciate any indication from community on this. > > Regards > Manish >
Regarding CASSANDRA-14227
Hi Team We are hit by this bug as we approach the deadline as we reach close to 2038 as we can see some of our projects breaching the deadline fixed. I can see some progress made in this bug by Berenguer Blasi in last few months. I do understand that review timings and development can not be predicted but it would be helpful in planning and updating our projects with some tentative dates/release when this bug can be targeted. I would appreciate any indication from community on this. Regards Manish
Re: Regarding CASSANDRA-14227
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 > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Regarding CASSANDRA-14227
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
