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 is there something subtly different now?" are onerous and worrysome to them.
If there's a clever, maintainable, and safe way to implement this change and be somehow backward compatible I could be on board. However, let's please keep the operators in mind when making these very externally visible changes. Thanks, -Jason On Mon, Dec 4, 2017 at 5:33 PM, Jon Haddad <j...@jonhaddad.com> wrote: > 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 <zznat...@gmail.com> wrote: > > > >> 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 unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
