Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: daf_butler
-
Story Points:2
-
Epic Link:
-
Sprint:DB_F20_06
-
Team:Data Access and Database
-
Urgent?:No
Description
For schema stability we need a place where we can store identifying information for schema itself and various configuration-related info as well. That will server as a sort of metadata for the rest of the schema and data in registry. To be usable from many releases it itself needs to be super-stable but we also should be be able to store all sorts of metadata in it, exact structure of that is not possible predict today. I think the most generic solution for that is a simple key-value store with arbitrary keys and values encoded as strings. All other structures can be mapped to key/value using reasonable rules, though some care is certainly needed to avoid name collision.
I think it is ready for review. The interface is now simplest possible, we may need to extend it later with new methods if needed. What is more important is the schema of the metadata table, I chose reasonably wide string types for both keys and values, I hope this should cover all our needs for now. We do not store any metadata yet, will work on that in next tickets.