[
https://issues.apache.org/jira/browse/OODT-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502730#comment-13502730
]
Luca Cinquini commented on OODT-522:
------------------------------------
Additional notes after issue was closed:
o Since the implementation of a lenient Lucene Catalog (OODT-529), it has
become possible to insert new metadata fields
o After more testing, it was noted that updating the metadata of an existing
product through this method led to a duplication of the "resource_*" fields,
since these fields are independently added by the Lucene catalog every time an
update request is received. This would eventually lead to a Lucene NPE because
the number of values would increase to more than what Lucene can handle. The
problem was fixed by having the Curator update() method remove the "resource_*"
fields, which are again added later on.
> 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
