[
https://issues.apache.org/jira/browse/OODT-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Cinquini resolved OODT-522.
--------------------------------
Resolution: Fixed
A new RESTful endpoint has been inserted "/metadata/update" that preserves all
current product metadata.
Example invocations:
curl --data "name=tns_dq219_01&metadata.NumberOfScans=1"
http://localhost:9080/curator/services/metadata/update
curl --data
"name=tns_dq219_01&metadata.NumberOfScans=1&metadata.NumberOfScans=2"
http://localhost:9080/curator/services/metadata/update
curl --data "name=tns_dq219_01&metadata.NumberOfScans=1&replace=false"
http://localhost:9080/curator/services/metadata/update
Note that at this time only existing metadata fields can be updated - the
validation layer prevents new undeclared metadata fields from being added.
> Curator REST endpoint for updating existing catalog metadata
> -------------------------------------------------------------
>
> Key: OODT-522
> URL: https://issues.apache.org/jira/browse/OODT-522
> Project: OODT
> Issue Type: Improvement
> Components: curator
> Affects Versions: 0.4
> Reporter: Luca Cinquini
> Assignee: Luca Cinquini
> Fix For: 0.5
>
>
> The current Curator endpoint for updating the catalog metadata:
> /services/metadata/catalog?id=...
> will add the supplied metadata, but remove all existing metadata for that
> product except for a handful of fields. This works well from the Curator web
> interface because the UI re-submits all currently existing metadata fields.
> In order to make it easier for other clients to update the metadata for a
> product, it is suggested that we supply a second endpoint (or change the
> current one) so that the current metadata for the requested product is not
> removed, but simply augmented with the new (key, value) pairs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
