Clarify Global Cache behavior when not caching a data instance#249
Merged
Conversation
Emphasising that a Global Cache shall publish WME if it decides not to cache an otherwise cacheable data instance.
golfvert
reviewed
Apr 16, 2026
Collaborator
golfvert
left a comment
golfvert
left a comment
There was a problem hiding this comment.
Remove "irregularity".
| * There is no requirement for a Global Cache to provide a browsable interface to the files in its repository in order to allow data consumers to discover what content is available. However, a Global Cache may choose to provide such a capability (for example, implemented as a WAF), along with documentation to inform data consumers of how the capability works. | ||
| * The default behaviour for a Global Cache is to cache all data published under the ``origin/a/wis2/data/+/core`` topic. A data publisher may indicate that data should not be cached by adding the ``"cache": false`` assertion in the WIS2 Notification Message. | ||
| * A Global Cache may decide not to cache data, for example, if the data are considered too large, or if a WIS2 Node publishes an excessive number of small files. If a Global Cache decides not to cache data, it should behave as though the cache property is set to false and send a message on the ``monitor`` topic hierarchy to inform the originating centre and its GISC. The Global Cache operator should work with the originating WIS2 Node and its GISC to remedy this issue. | ||
| * A Global Cache may decide not to cache data, for example, if the data are considered too large, or if a WIS2 Node publishes an excessive number of small files. If a Global Cache decides not to cache data, it should behave as though the cache property is set to false and shall send a WME (WIS2 Monitoring Event) message on the ``monitor`` topic hierarchy to inform other centres about this irregularity. The Global Cache operator should work with the originating WIS2 Node and its GISC to remedy this issue. |
Collaborator
There was a problem hiding this comment.
I would suggest replacing "other centres about this irregularity" with "WIS Centres". I would not qualify this as an irregularity by definition. We wrote in the guide that it was a possibility to do this. So, according to the spec, it is "regular" as allowed.
…n no data instance is cached
golfvert
approved these changes
Apr 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Emphasising that a Global Cache shall publish WME if it decides not to cache an otherwise cacheable data instance.