-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
add Global Replay (#143) #144
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments, points to discuss.
I don't understand how users will get the data.
On the HTTPS stream ?
@golfvert thanks for the feedback. Updates pushed. Let me know if there are additional issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Purely editorial revisions suggested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed "the" from wis2-grep.
144b16a
to
eedd477
Compare
* Global Replay instances operate independently of each other; each Global Replay instance will hold notification messages according to the required retention period. Global Replays do not need to synchronise between themselves. | ||
* A Global Replay is populated with notification messages from a Global Broker instance. | ||
* A Global Replay should connect and subscribe to more than one Global Broker instance to ensure that no messages are lost in the event of a Global Broker failure. A Global Replay instance will discard duplicate messages as needed. | ||
* A Global Replay will validate notification messages against the WIS Notification Message (WNM). Valid WIS Notification Messages will be ingested into the index. Invalid or malformed notification messages will be discarded. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No real need to check. No problem though, to do it again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to can
The usable API is not defined. Is that on purpose ? We may have different Global replay providing different API. Is that what we want ? |
In GRep Technical Considerations, we define the API per:
|
@golfvert @tomkralidis Is this issue ready for FT2024-2 or does it need more conversation/review? I'm finalizing all proposals this week. |
It is too soon to be in the FT. We haven't had a proper discussion in the team. |
Fixes #143