Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
7.0.0
-
Untriaged
-
1
-
No
Description
Once user has chosen custom mappings, and hit save, there is no more easy-to-read alert to show whether or not specific mappings are valid or broken.
The only choice for users right now is to go to the UI "Log" section and read plain text.
If UI can find a way to display broken mappings, then XDCR can provide a real-time update of what is broken, and users can be made aware of what collections are not being backed up/replicated and are subjected to errors.
XDCR backend work is tagged as MB-43352
Update: MB-45847 will show a error message in the UI with a permenant badge count of 1 as long as brokenmap exists.
Attachments
Issue Links
- depends on
-
MB-43352 XDCR to pass brokenMapping via errorsList
- Closed
- is duplicated by
-
MB-45771 [System Test][UI] XDCR Errors displaying just the timestamp and no message body
- Closed
- relates to
-
MB-38507 Post brokenMapping to replicationStatus for UI to digest
- Closed
-
MB-45847 XDCR - BrokenMap events should output a "summary" errorMsg
- Closed
- links to