Property tables for the config store
Reported by Ben Hood | February 3rd, 2011 @ 06:00 PM | in 0.9.3
We need to include some general metadata tables into the config store to record general properties about diffa.
Some properties that we need to configure are:
- The version of the config store schema (so that subsequent releases of diffa can auto-migrate the database)
- Persistent properties (that are currently defined in the
diffa.properties file):
- The diffa.properties should ultimately be retired and be replace by DB properties
- To set the properties we should implement a remote call - this is tied to a little to #43
Comments and changes to this ticket
-

Ben Hood February 4th, 2011 @ 02:48 PM
- Milestone set to 0.9.3
- Milestone order changed from 13 to 0
-

Paul Jones February 7th, 2011 @ 08:40 AM
- State changed from new to open
- Assigned user set to Paul Jones
-

Ben Hood February 7th, 2011 @ 10:21 AM
(from [ea83718499b7f1090318ccd898d203d49d452717]) [#169] Read agent configuration options from database instead of properties file. https://github.com/lshift/diffa/commit/ea83718499b7f1090318ccd898d2...
-

Paul Jones February 7th, 2011 @ 10:23 AM
- State changed from open to resolved
- Assigned user changed from Paul Jones to Ben Hood
I've implemented this in a very basic form. Previous references in the Spring Config to loaded properties are replaced with a call to the ConfigStore. This gives us pretty good compatibility with what we have now (excluding the fact that without #43 there is no way to override defaults).
I think in the future, we might want to consider making the access to the properties slightly more dynamic, since quite a few properties should be changeable without requiring an agent restart (this would require the usage of them to move toward a more pub-sub mechanism, instead of the string injection being done currently).
-

Ben Hood February 7th, 2011 @ 12:38 PM
- State changed from resolved to open
- Assigned user changed from Ben Hood to Paul Jones
I've create #175 to follow up with the dynamic aspects of property loading.
#176 now marks the store migration.
Reopening because the versions of the {ConfigStore,CorrelationStore} are not persisted as config values. While you're doing this, could you make sure that the versionCorrelationStore stanza in the applicationContext.xml is correctly aligned.
-

Ben Hood February 8th, 2011 @ 02:41 PM
(from [d8587d4cb14b83f488beddc51846eb2a1b2c7759]) [#169] Store configStore and correlationStore schema versions as config options. https://github.com/lshift/diffa/commit/d8587d4cb14b83f488beddc51846...
-

Paul Jones February 8th, 2011 @ 02:41 PM
- State changed from open to resolved
- Assigned user changed from Paul Jones to Ben Hood
- Fixed the alignment issues;
- Persisting versions of the schemas, and some basic code for checking their current values;
-

-

-

Paul Jones February 11th, 2011 @ 09:58 AM
- State changed from closed to resolved
-

Paul Jones February 11th, 2011 @ 09:58 AM
- State changed from resolved to open
-

Paul Jones February 11th, 2011 @ 10:00 AM
- State changed from open to closed
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
People watching this ticket
Tags
Referenced by
-
169
Property tables for the config store
(from [ea83718499b7f1090318ccd898d203d49d452717])
[#169] ...
-
175
Dynamic Configuration Mechanism
#169 introduced a table for persisting Diffa
level proper...
-
176
Store Migration
In #169, the versions of the
{ConfigStore,CorrelationStor...
-
169
Property tables for the config store
(from [d8587d4cb14b83f488beddc51846eb2a1b2c7759])
[#169] ...
-
169
Property tables for the config store
(from [f68f381b0de087d0c385365c7b6ced3bbcc9a61e])
Merged ...