Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
avatar image
Question by asiri.rathnayake · Aug 15, 2017 at 09:28 AM · ETAmrn_storyelecktronscalingredundancy

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

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by Eric Fischkin · Aug 15, 2017 at 12:32 PM

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.

Comment

People who like this

0 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
Peter Ficzere · Aug 16, 2017 at 03:39 AM 0
Share

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."

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
10 People are following this question.

Related Questions

Redundancy subscribers

MRN field coupling with old News Feed Direct

Submit of CloseMsg failed

Elektron news

Why is "MRN Data Models and Elektron Implementation Guide" missing field messageType

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges