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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAMAYA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722321#comment-16722321 ] 

ASF subversion and git services commented on TAMAYA-372:
--------------------------------------------------------

Commit 6ab216df0ec6081cd35c1847048b6dab93d1b3bf in incubator-tamaya's branch refs/heads/master from [~anatole]
[ https://gitbox.apache.org/repos/asf?p=incubator-tamaya.git;h=6ab216d ]

TAMAYA-372: Clarified default metadata format.


> 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
>            Priority: Major
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> 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)