Changing the name of the item in the get_timeseries() call throws an exception
The following get_timeseries() call to retrieve the S&P 500 index returns proper data:
However, if I simply change the name of the item to retrieve Microsoft data, the get_timeseries() call throws an exception.
Looking at the details of the above error, it seems there is no data available for MSFT.O. If that is the case, wouldn't returning a result with zero rows imply that?
Answers
-
Hi Nick, Microsoft got listed in March 1986, that's why you get an error...
0 -
Thanks for the update. Yes, I was actually looking to see what would happen when I chose a date prior to them being listed. I was expecting no data, not an exception. When I use the get_data() call, the response is different:
0 -
Maybe this could be raised as an enhancement request?
0 -
I just re-tested this functionality with the latest version at this time (0.1.13), and the error returned is much more descriptive:
If throwing an exception is the appropriate result if no data is available, I would expect consistent behavior when requesting using the get_data() function call. However, the get_data() doesn't throw an exception, it returns no data.
0 -
@nick.zincone What I can capture from your reply is that the result when there is no data available from get_data() and get_timeseries() functions are different, am I correct? What is the expected behavior? Should it be (1) throwing an exception only, or (2) no data only?
Please specify. So, @Joris.Hoendervangers can understand how Eikon Data API should behave against each particular situation and communicate with the Development team thereafter.
0 -
What the response should be is consistent. Both method calls should respond in the same way. What way do I suggest? Well in this case, both responses should return no data. Exceptions usually indicate something a little more severe like passing in a wrong type to the method call.
0 -
I agree with @nick.zincone. I think an exception is inappropriate here. It's worth noting that in the current implementation the exception is only thrown if there's no data for all RICs in the request. If the timeseries exist for at least one RIC in the request, then no exception is raised and the data is returned, but only for the RICs that have timeseries in the specified range. I would prefer if get_timeseries method returned a tuple with the dataframe and error like get_data method does.
0 -
I also would prefer if the dataframe returned by get_timeseries method contained empty strings or NaNs for the RICs that don't have timeseries in the specified range instead of current behavior that omits these RICs from the dataframe altogether.
0 -
@Joris.Hoendervangers, can you please respond to the additional request from @nick.zincone?
0 -
Which question?
0 -
I think @Nipat Kunvutipongsak means this question:
Please specify. So, @Joris.Hoendervangers
can understand how Eikon Data API should behave against each particular
situation and communicate with the Development team thereafter.0 -
@Joris.Hoendervangers, I'd like to quote their responses here:
From Nick:
What the response should be is consistent. Both method calls should respond in the same way. Well in this case, both responses should return no data. Exceptions usually indicate something a little more severe like passing in a wrong type to the method call.
From Alex:
I agree. I think an exception is inappropriate..So, I think you should contact @nick.zincone and @Alex Putkov.1 directly for more details on this requirement, who are the Eikon Data API user's that explain the expected result from the situation given.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 687 Datastream
- 1.4K DSS
- 621 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 669 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛
