Seeing metadata error when subscribing to streaming summaries for specific instruments
In the HistoricalPricing - TSInterday project we're subscribing to streaming summaries with a Daily interval and are receiving the following error: "Error: Failed to load meta data. Failed to load Instrument Metadata for item: AUA04000524=WPAC". The same error is returned for US1DCP=. Here is the code that can duplicate the problem...
// Create the platform session.
using ISession session = Sessions.GetSession();
// Open the session
session.Open();
var stream = Summaries.Definition("AUA04000524=WPAC")
.Interval(Summaries.Interval.P1D)
.GetStream();
// Specify the TSI lambda expressions to capture 'Insert' and 'Update' events
stream.OnInsert((data, stream) => Common.DisplayTable($"INSERT: {DateTime.Now}", data.Table))
.OnUpdate((data, stream) => Common.DisplayTable($"UPDATE: {DateTime.Now}", data.Table))
.OnStatus((status, stream) => Console.WriteLine($"Status: {status}"))
.OnError((error, stream) => Console.WriteLine($"Error: {error}"))
.Open();
Console.ReadLine();
}
catch (Exception e)
{
Console.WriteLine($"\n**************\nFailed to execute: {e.Message}\n{e.InnerException}\n***************");
}
Best Answer
-
Based on my initial investigation, there doesn't appear to be any metadata associated with the instruments you highlighted. The library is simply reacting and reporting it is unable proceed because metadata rules are at the heart of the processing.
We'll need to follow-up with the server team to report this issue. You did note 2 instruments, if you have any others, please share and we'll provide the team these details.
thanks.
0
Answers
-
Hello @cory.schmidt.1
The error seems to be caused by a parsing issue of the incoming response for the instruments used in the example. Could you please provide any generated logs ?
Thanks,
Cristian
0 -
I can replicate this error.
The debug log looks like this:
Application: Debug - Preparing Endpoint GET request http://localhost:9001/api/rdp/data/historical-pricing/v1/metadata/global-metadata
Application: Info - Successfully loaded the Global Metadata database.
Application: Info - Completed global metadata parsing
Application: Debug - Preparing Endpoint GET request http://localhost:9001/api/rdp/data/historical-pricing/v1/metadata/instrument-metadata?version=v2&types=MarketRulesData,Qualifiers,RuleReferenceData,TimeZone,TradingSessions&ric=AUA04000524%3DWPAC
Application: Warn - Failed to extract 'TimeZone' element. Defaulting to: GMT
Application: Error - Failed to extract 'MarketRulesData.dataFilterClauses' stanza
{}
Application: Error - Failed to load Instrument Metadata for item: AUA04000524=WPAC. Failed to parse metadata
Application: Error - Failed to retrieve Instrument Metadata
Error: Failed to load meta data. Failed to load Instrument Metadata for item: AUA04000524=WPAC0 -
@Jirapongse
Thank you for the help !
@cory.schmidt.1By looking at the logs it seems that the incoming object is empty.
I will start my investigation into this issue.
0 -
My initial observation that the incoming response is empty was correct.
It seems that the endpoint is responding with a 200 (OK) http status code, but there is no content for us to parse.
Continuing investigation...
0 -
It seems that retrieving summary data (not streaming) works, using a simple endpoint definition, like this:
var universe = "AUA04000524=WPAC";
var url = "https://api.refinitiv.com/data/historical-pricing/v1/views/interday-summaries";
var endpoint = $"{url}/{universe}";
var response = EndpointRequest
.Definition(endpoint)
.QueryParameter("interval", "P1D")
.GetData();I will continue investigating to see why there is no data for streaming...
0 -
What I found so far is that instrument metadata is the object not retrieved for AUA04000524=WPAC , but I haven't found the reason why yet. I am using the exact same example code and replacing the faulty instrument with EUR= and I have no issues...
Instrument metadata is something we cannot ignore as being null or empty because it is used in streaming for normalization of incoming records based on data filter clauses and rules in order to obtain correct data.
There are also no errors, warnings or other information coming back with the response.
I will probably need to discuss with @nick.zincone about this issue next week to gain more knowledge...
0 -
Should you require a content enhancement, you just need to raise a support ticket via my.refinitiv site the same way you raise support tickets for any other product/content concerns and once support receives it they'll go through the process from there.
Br,
Cristian
0 -
Thanks, I'll get that raised today.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 中文论坛