You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Anatole Tresch (JIRA)" <ji...@apache.org> on 2018/12/11 09:59:00 UTC

[jira] [Created] (TAMAYA-372) Clarifiy/isolate metadata format

Anatole Tresch created TAMAYA-372:
-------------------------------------

             Summary: Clarifiy/isolate metadata format
                 Key: TAMAYA-372
                 URL: https://issues.apache.org/jira/browse/TAMAYA-372
             Project: Tamaya
          Issue Type: Improvement
          Components: API, Core, Extensions
    Affects Versions: 0.3-incubating
            Reporter: Anatole Tresch
            Assignee: Anatole Tresch


Currently we use different metadata formats:
 * {{like etcd: starting with an '_', e.g. _a.b.c.meta=ghfghgf}}
 * {{Using a bracket stype prefix similar to log formats: [META]a.b.c.meta=ghfghgf}}

The proposal is to
 * Add a *MetaDataProvider* SPI that
 ** extracts metadata inline with the config entries.
 ** extracts metadata from the property value metadata entries
 ** supports adding metadata also programmatically

Along with that the default metadata format should be changed to:

{{[(META)a.b.c].meta=ghfghgf}}

This allows for future extensions of metadata types and defines a clear parseable structure for adding metadata along the configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)