Skip to content

FT2025-2 update #205

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 13, 2025
Merged

FT2025-2 update #205

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dfd62fa
move properties.global-cache requirement #190
amilan17 Aug 13, 2025
de2e84f
Update global-services.adoc
amilan17 Aug 13, 2025
8f635b6
Update global-services.adoc
amilan17 Aug 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion guide/sections/part2/global-services.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,6 @@ In WIS2, Global Caches provide access to WMO core data for data consumers. This
* For messages received on the topic ``++origin/a/+/data/core/#++`` or ``++cache/a/+/data/core/#++``, a Global Cache shall:
** If the message contains the property ``"properties.cache": false``,
*** Republish the message at topic ``cache/a/wis2/...``, matching ``+/a/wis2/...`` where the original message has been received, after having updated the id of the message.
** Add the property ``properties.global-cache`` with the value of the centre identifier of the Global Cache to identify the origin of the data source downloaded by downstream applications.
** Else
*** Maintain a list of ``data_id`` values that have already been downloaded;
*** Verify whether the message points to new or updated data by comparing the pubtime value of the notification message with the list of ``data_id`` values;
Expand All @@ -140,6 +139,7 @@ In WIS2, Global Caches provide access to WMO core data for data consumers. This
**** If the message contains an integrity value for the data, verify the integrity of the data;
**** If data is downloaded successfully, move the data to the HTTP endpoint of the Global Cache;
**** Wait until the data becomes available at the endpoint;
**** Add the property ``properties.global-cache`` with the value of the centre identifier of the Global Cache to identify the origin of the data source downloaded by downstream applications;
**** Modify the message identifier and the canonical link's ``href`` of the received message and leave all other fields untouched;
**** Republish the modified message to topic ``cache/a/wis2/...`` ,matching the ``+/a/wis2/...`` where the original message has been received;
**** The metric ``wmo_wis2_gc_downloaded_total`` will be increased by 1; The metric ``wmo_wis2_gc_dataserver_last_download_timestamp_seconds`` will be updated with the timestamp (in seconds) of the last successful download from the WIS2 Node or Global Cache;
Expand Down