Missing keys in delete action when dealing with MarketByOrder domain.
I'm trying to build a book based on Market-By-Order.
But I've observed there are missing keys.
For example,
as for key "NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQyNw==",
{"Action":"Delete","Key":"NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQyNw=="} was received but there was no existing entry for the key thsin9.txto delete.
There were a lot of missing keys like this.
Please refer to the attached and below missing keys and advise on how to deal with it properly.
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQyNw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQ2Mw==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MjQ2OQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MjUxMQ==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU0Ng==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU0Nw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU5Nw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU5Ng==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MjYxMg==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU5OA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjU5MA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjcyMA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjczNA==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MjgxNQ==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjgyOA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5Mw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5Mg==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5NQ==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5NA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4Mjg5OA==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4Mjk5Ng==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzAxMQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzEyOQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzE1OQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzEzOQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzE5Mg==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzIxNQ==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzIxOA==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzI2MA==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzI2MQ==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzI2Mw==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzMxMA==
NzI2ODM0MjZBNzE2MTk3MDU0MTQ3MjQ4MzQ2Mg==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzUwOQ==
NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MzUyMg==
Best Answer
-
Hi @changgyu,
I have verified historical data from TRTH and found an update with "Add" action for the missing key entry (i.e. NzI2ODM0MjZCNzE2MTk3MDU0MTQ3MjQ4MjQyNw==) sent from Elektron Realtime feed. (Please note that the key actually was base64 encoded. The actual key is "72683426B7161970541472482427".)
Please contact ERT in cloud support via MyRefinitiv to verify the issue.
Below is the detailed information I found when compare data between application log and historical data from TRTH.
- An update was provided to add entry for "72683426B7161970541472482427" key.
HSIN9,Market By Order,2019-07-17T07:01:33.725528358Z,+8,Raw,UPDATE,UNSPECIFIED,,,,9020,,25968,,0
,,,,Summary,,,,,,,,,,2
,,,,FID,4148,,TIMACT_MS,25293631,
,,,,FID,6516,,BOOK_STATE,1,N
,,,,MapEntry,,ADD,,,,,,72683426B7161970541472482427,,9
,,,,FID,14268,,LV_TIM_NS,07:01:33.631438000,
,,,,FID,8591,,ORD_TONE,0,
,,,,FID,6919,,ORDER_PRIY,26284031,
,,,,FID,3428,,ORDER_SIDE,1,BID
,,,,FID,13439,,ORDER_TN,0," "
,,,,FID,3429,,ORDER_SIZE,1,
,,,,FID,6529,,LV_DATE,2019-07-17,
,,,,FID,3427,,ORDER_PRC,28562,
,,,,FID,3426,,ORDER_ID,7161970541472482427,- The update is expected to be added in this entrysequence.txt. ( I have added base64 decoded for Map Entry keys.
0
Answers
-
Hello @changgyu
I suggest you contact the feed team to verify if the feed sent correct data(delete action on non-existing key) or not. You can contact the feed team via Get Support of MyRefinitiv and select Product to be the feed i.e Thomson Reuters Elektron Real-Time .
Delete action indicates that the consumer should remove any stored or displayed information associated with the entry. As far as I understand, for delete action on non-existing key case, it is possible that the application will ignore the delete action because the key does not exist when the delete action comes. Normally, delete action should for existing key so you should contact the feed team to verify data as well.0
Categories
- All Categories
- 6 AHS
- 37 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛