-
Notifications
You must be signed in to change notification settings - Fork 2
Registry Workshop 2022‐01‐24
- Review of the Registry
- OpenSearch Architecture
- Review Requested Changes & Bugs
- Q&A
Meeting Recording: https://jpl.webex.com/jpl/ldr.php?RCID=cc0692edfd380707a6134a6b4ad0189b
Cluster/scalable configuration (Jimmie), as fix for bug #132
A change of configuration is going to be done to use the 3 nodes of each OpenSearch database (one for each discipline node).
Jimmie is going to contact each discipline node to schedule the upgrade. The upgrade for GEO node is on-going. None of the other node reached a volume limit.
Bug on update: #118
Update by package-id: #131
Dashboards/requests:
Matt: request on all entries referring to a specific LID.
Answer: The following API request enable this, urn:nasa:pds:context:investigation:mission.orex being the LID which references are searched for:
curl --get 'https://pds.nasa.gov/api/search/1.0/products' \
--data-urlencode 'limit=200' \
--data-urlencode 'q=((pds:Internal_Reference.pds:lid_reference eq "urn:nasa:pds:context:investigation:mission.orex") or (pds:Internal_Reference.pds:lid_reference like "urn:nasa:pds:context:investigation:mission.orex::*"))' | json_pp
Dan: what to do when products are superseded and the artifacts are moved from one location to another.
Answer: change the path directly in the OpenSearch database or re-ingest all the label updated with new path. If the artifacts are offline we would need a splash page telling that the data is now offline.
Pat:: is there a superseded or offline archive status
Answer: not yet. That would need a discussion with the DDWG.
- Jimmie is going to contact each discipline node to schedule registry upgrade for B13.0
- EN to provide Matt T. with example of querying for all products that reference a particular product LID
- Review and revise B13.1 plans based upon feedback and inputs from group