cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-4998) Add hook for modifying configuration after cassandra.yaml is loaded
Date Fri, 04 Jan 2013 11:10:13 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne resolved CASSANDRA-4998.
-----------------------------------------

    Resolution: Won't Fix

Closing that one in favor of CASSANDRA-5045 then.
                
> 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

Mime
View raw message