You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/12/01 22:53:58 UTC
[jira] [Updated] (CASSANDRA-4998) Add hook for modifying
configuration after cassandra.yaml is loaded
[ https://issues.apache.org/jira/browse/CASSANDRA-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4998:
--------------------------------------
Reviewer: slebresne
Priority: Minor (was: Major)
Issue Type: New Feature (was: Improvement)
I'm definitely not a fan of "let's override things programatically instead of just updating the yaml;" that is a great way to shoot yourself in the foot.
Will let Sylvain weigh in on if this is useful enough for dtests to include anyway.
> Add hook for modifying configuration after cassandra.yaml is loaded
> -------------------------------------------------------------------
>
> Key: CASSANDRA-4998
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4998
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Michael Guymon
> Priority: Minor
> Labels: patch
> Attachments: 0001-Add-load-hook-for-updating-Config-before-processing.patch, 0002-Remove-the-need-for-separate-cassandra.yml-in-tests.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: http://www.atlassian.com/software/jira