cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Guymon (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4998) Add hook for modifying configuration after cassandra.yaml is loaded
Date Sat, 01 Dec 2012 20:47:58 GMT


Michael Guymon commented on CASSANDRA-4998:

Correct me if I am wrong, but embedding Cassandra does not prevent it from being in a cluster.

The goal I am trying to get at is to allow runtime configuration of Cassandra when it inits,
instead of only relying on the cassandra.yaml. This will allow Cassandra to be embedded with
other services and be part of a standardize configuration process. 

This patch is not very invasive, just adds the option for a callback when the cassandra.yaml

One of the added benefits of this patch is it make testing easier. By using the callback hook
to toggle settings, the conditional processing in DatabaseDescriptor can be asserted. It should
allow tests that use an embedded Cassandra to use the callback instead of generating a cassandra.yaml
on the fly based on a template.

> Add hook for modifying configuration after cassandra.yaml is loaded
> -------------------------------------------------------------------
>                 Key: CASSANDRA-4998
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Michael Guymon
>              Labels: patch
>         Attachments: 0001-Add-load-hook-for-updating-Config-before-processing.patch,
> When embedding Cassandra in an application, allow programmatic changes to Cassandra's
config by using a hook to modify the configuration after the YAML is loaded. 
> For this to work, a new YAML configuration needs to be added: after_load_hook_class.
If defined, it would be the FQN of a class that implements IAfterLoadHook. When DatabaseDescriptor
calls loadYAML(), before any processing of the Config happens, the after_load_hook_class is
checked and called if exists. Then processing of the config happens as normal.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message