De-duplicating MRN_STORY messages received over two subscriptions
Hello,
(First post here).
For redundancy, we have two news handler processes (primary & secondary) subscribing to the MRN_STORY RIC over the ELECTRON_DD service. In our backend, we would like to de-duplicate the messages received over these two feeds so that only a single "master" copy of a news item is kept in the database. This brings a couple of questions:
1. Is it possible for the "same" news item to be published over two different MRN_SRC systems? (If this is the case, it would mean we cannot use the MRN_SRC-GUID combination as a unique identifier in the backend for de-duplication of messages - as our primary and secondary news handler processes may receive the same message over different MRN_SRC systems).
2. If the answer to (1) is "Yes", what other fields should we be looking at for redundancy removal? Perhaps we can hash some combination of fields in the JSON body of the message? But it's unclear from the documentation what fields should be used for this kind of a setup.
3. Is there a correlation between the messages received over MRN_STORY RIC and the MRN_TRNA RIC? (I'm wondering if such a relationship can be exploited for redundancy removal).
Thanks!
/ Asiri
Best Answer
-
Duplicate news items share GUID values alone.
De-duplication among messages also is important. Consumers may observe them after a failover in Thomson Reuters infrastructure. In this case, the duplicate messages would share GUID and FRAG_NUM values.
The "id" field in the JSON links news items across MRN_STORY and MRN_TRNA.
0
Answers
-
Thank you for your quick response.
Just to clarify: Does a story has the same GUID no matter which MRN_SRC it is coming from?
After reading the spec I thought only GUID+MRN_SRC does uniquely identify a story (which would question why GUID is called GUID).
MRN DATA MODELS AND ELEKTRON IMPLEMENTATION GUIDE DATA MODEL VERSION 2.10, NEWS ANALYTICS VERSION 3.1
Section 3.2.1.2 "A single MRN data item publication is uniquely identified by the combination of RIC, MRN_SRC and GUID."
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛