[
https://issues.apache.org/jira/browse/OODT-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570742#comment-13570742
]
Rishi Verma commented on OODT-555:
----------------------------------
Hi Luca,
Thanks for your help on this.
I just tested curator trunk rev. 1442427 and it seems that it doesn't display
the expected behavior with the Lucene backend.
I performed the reproducibility steps outlined above, including issuing a curl
invocation to update a metadata key/value, but the result of that action was
that all the metadata for the product I was seeking to update was removed.
Thus, the problem is no longer that the product is deleted upon an metadata
update action, but that all the product's metadata disappears.
Let me spend some time later to investigate, but you mentioned in your RB post
[1] that the fix worked for your Lucene-based catalog instance? I'm curious if
you tried the exact curl call shown above?
Thanks Luca!
--
[1] https://reviews.apache.org/r/9257/diff/#index_header
> CAS-Curator MetadataResource REST endpoint updateMetadata deletes product met
> instead of updating
> -------------------------------------------------------------------------------------------------
>
> Key: OODT-555
> URL: https://issues.apache.org/jira/browse/OODT-555
> Project: OODT
> Issue Type: Bug
> Components: curator
> Affects Versions: 0.6
> Reporter: Rishi Verma
> Assignee: Luca Cinquini
> Priority: Critical
> Fix For: 0.6
>
> Attachments: OODT-555-stacktrace.txt
>
>
> The trunk build of CAS-Curator (rev. 1440737) seems to break the
> MetadataResource.updateMetadata method by deleting product met instead of
> updating it.
> I built a trunk build of cas-curator webapp and deployed to a local tomcat.
> Next, I pointed the curator to my local cas-filemgr. From this point,
> following the CAS-Curator REST API directions for updating a product's
> metadata [1], I attempted to invoke a sample call to update a metadata field.
> This step had two consequences: (1) the product's metadata was not updated,
> and critically (2) the product was actually deleted!
> Reproducibility steps:
> 1. Build latest trunk build (rev. 1440737) of curator
> 2. Deploy to tomcat with an active filemgr catalog (containing data)
> 3. Invoke the following Unix command to update the metadata for a given
> product: curl --data
> "id=<YOUR_PRODUCT_ID>&metadata.<METADATA_KEY_NAME>=<METADATA_KEY_VALUE>"
> http://localhost:8080/curator/services/metadata/update
> 4. Watch to see the product met actually being deleted instead of updated
> I will attach the stack trace (seen from step 4) to this bug report.
> --
> [1] https://cwiki.apache.org/OODT/cas-curator-rest-api.html
--
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
