[
https://issues.apache.org/jira/browse/CASSANDRA-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273764#comment-16273764
]
Jon Haddad commented on CASSANDRA-13976:
----------------------------------------
I'd actually like to get some feedback on -dev regarding this. I'd like to
change *every* setting to use duration types, because it makes it less error
prone to set. Mistyping a millisecond based config is pretty easy and hard to
catch when it's wrong.
> introduce max_hint_window_in_min, deprecate max_hint_window_in_ms
> -----------------------------------------------------------------
>
> Key: CASSANDRA-13976
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13976
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jon Haddad
> Assignee: Kirk True
> Priority: Minor
> Labels: lhf
> Fix For: 4.0
>
>
> Milliseconds is unnecessarily precise. At most, minutes would be used.
> Config in 4.0 should default to a minute granularity, but if the
> max_hint_window_in_min isn't set should fall back on max_hint_window_in_ms
> and emit a warning.
> max_hint_window_in_min: 180 # new default, still at 3 hours.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
