You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kurt Greaves (JIRA)" <ji...@apache.org> on 2018/02/12 00:26:00 UTC
[jira] [Commented] (CASSANDRA-14095) New configuration settings
using duration types
[ https://issues.apache.org/jira/browse/CASSANDRA-14095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360185#comment-16360185 ]
Kurt Greaves commented on CASSANDRA-14095:
------------------------------------------
trawling through Jira and apparently we already had a ticket for this. CASSANDRA-9691. [~rustyrazorblade] I'll leave it to you to decide which one to close as duplicate.
> New configuration settings using duration types
> -----------------------------------------------
>
> Key: CASSANDRA-14095
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14095
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jon Haddad
> Assignee: Jon Haddad
> Priority: Major
>
> All the _ms configuration params are difficult to work with. We can allow users to provide a duration type, like 3h, for settings instead of requiring _ms based settings.
> This first jira is to allow for cassandra.yaml to take duration types instead of ms based settings.
> Given a setting, blah_ms, the new setting should be {{blah}} and require a duration like {{3h}}. The old _ms settings should continue to work and error if both are used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org