We will have to deal with fixing this TTL issue eventually as more users start to deal with the boundaries of currently allowed TTL (which keeps declining). It will be neat if we can get this into 4.0 before it is released - be it in beta or future 4.0 alpha(s) - the sooner the better, as everyone in the community gets busy validating 4.0 bits.
Thanks, Sumanth On Tue, Sep 17, 2019 at 7:33 AM Benedict Elliott Smith <bened...@apache.org> wrote: > 1. During ApacheCon, Laxmikant approached me to discuss > CASSANDRA-14227. It was also raised on the list back in January. > > > > Taking a closer look, it probably is not very difficult for us to fix this > – either by treating the int as unsigned, or by widening it to a long > value. Since this can only easily be done once per major version, and the > number of representable dates is steadily declining, there’s a strong case > to be made for delivering this for 4.0-beta. > > > > The least invasive change is probably to simply permit negative values, > and to treat them as unsigned. However, this or using long would both be > modest changes. > > > > Does anyone have any strong thoughts or opinions on this? > >
