[
https://issues.apache.org/jira/browse/CASSANDRA-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508189#comment-13508189
]
Michael Guymon commented on CASSANDRA-4998:
-------------------------------------------
I should bring up, the scenario I am attempting, the cassandra.yaml would be
package and loaded from the classpath, not exposed directly. There is no foot
violence by having to manage multiple configs.
That being said, this patch would not affect the current way Cassandra runs.
Only if someone rolls their own hook, updates the start up of Cassandra so it
loads into the classpath, and then explicitly sets it in the cassandra.yaml.
> 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
