[
https://issues.apache.org/jira/browse/TAMAYA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722323#comment-16722323
]
ASF subversion and git services commented on TAMAYA-372:
--------------------------------------------------------
Commit 74a7a9b18ae548c6fa053c69877e3c19460315e5 in
incubator-tamaya-extensions's branch refs/heads/master from [~anatole]
[
https://gitbox.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=74a7a9b
]
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)
