get_timeseries ignored start date,returns full Data history

Received report from our big client.
ek.get_timeseries() ignored start date, return all of history data,
not just return data from start date to end date.
Seems not an expected behaviour, could you help investigate and give feedback.
sample code:
data_16pm = ek.get_timeseries(["XAU="],
fields='CLOSE',
start_date=date.astype('M8[ms]').astype('O') + datetime.timedelta(hours=8),
end_date=date.astype('M8[ms]').astype('O') + datetime.timedelta(hours=8),
interval='hour')
I found below link,seems it's a bug with an underlying time series service.
but didn't found any fixed plan or fix schedule.
If this issue is a bug, could you help check when will fix it.
or if you can provide any workaround.
https://community.developers.refinitiv.com/questions/6355/view.html
Title: bug in get_timeseries
https://community.developers.refinitiv.com/questions/22759/get-timeseries-returns-full-dataframe-when-queried.html
Title: get_timeseries returns full DataFrame when queried for holidays.
https://community.developers.refinitiv.com/questions/13936/eikon-api-proxy-timeseries-start-date-ignored.html?childToView=14655#answer-14655
Title: Eikon API proxy timeseries start date ignored
Best Answer
-
0
Answers
-
@Olivier DAVANT Add sample code and output to you.
Code:
import eikon as ek
ek.set_app_id('XXXXXXXX')
ek.set_timeout(2000)
fx1 = ek.get_timeseries(
"XAU=",
fields='CLOSE',
start_date="2018-05-09T09:00:00",
end_date="2018-05-09T13:00:00",
interval='hour')
print(fx1)Output:
XAU= CLOSE
Date
1968-03-22 40.0000
1968-03-25 40.2500
1968-03-26 41.1000
..........
2018-05-08 1314.0800
2018-05-09 1310.3600[12577 rows x 1 columns]
0 -
Thanks for your answer.
But I tested used below code, returns full Data history. please help take a look.
fx1 = ek.get_timeseries(
"XAU=",
fields='CLOSE',
start_date="2018-05-16T01:01:00",
end_date="2018-05-16T01:01:00",
interval='hour')
fx1 = ek.get_timeseries(
"USD=",
fields='CLOSE',
start_date="2018-03-16T01:01:00",
end_date="2018-05-16T01:01:00",
interval='hour')0 -
In your example there's no point in the hourly timeseries that falls between the start_date and end_date. As a result I would expect the service to return either an error or an empty result, not the entire timeseries available from default daily interval. I'll raise this issue.
0 -
@Alex Putkov, thanks for your answer. It's very appreciate if we can set a schedule for this.
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 中文论坛