I like this idea, but tbh I hate overburdening operators with what will
seem them as busywork. Operators have scripts and other infrastructure to
automate the creation of yaml files, and the thoughts of "oh crap, why did
they rename all the properties? And, are these really just simple renames,
or
Sure, I’m fine w/ letting the _ms settings work indefinitely. Can revisit
retiring them if there’s ever a real need, am OK if that never happens.
I’ll create the JIRA.
> On Dec 4, 2017, at 5:19 PM, Nate McCall wrote:
>
>> I'd be in favour of never retiring the _ms format though - it's almost
> I'd be in favour of never retiring the _ms format though - it's almost
> free, there's no backward compatibility problems, and it's fairly intuitive
> so long as we're consistent about it.
>
Agreed on this point. Overall, this will be excellent for usability.
---
To be clear I’m not -1 on this, I just hope we think about upgrading users as
we deprecate the old stuff out
--
Jeff Jirsa
> On Dec 4, 2017, at 4:24 PM, Jon Haddad wrote:
>
> I ways back I had entire CASSANDRA-13976 out of sheer annoyance to change the
> hint time to be in minutes instead
I'm strongly in favour of it; it's always bugged me, and I hadn't realised
it might be contentious to implement.
I'd be in favour of never retiring the _ms format though - it's almost
free, there's no backward compatibility problems, and it's fairly intuitive
so long as we're consistent about it.
I ways back I had entire CASSANDRA-13976 out of sheer annoyance to change the
hint time to be in minutes instead of ms. Millisecond based resolution is a
bit absurd for things like hints. I figured minutes would be better, but after
some back and forth realized durations (3h, 30m, etc) would b
