New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rblapi: upgrade to bloomberg api 3.11.6.1 #276
Comments
The public API download page (https://www.bloomberg.com/professional/support/api-library/) still has 3.8.18.1 as supported release, with 3.11.6.1 referenced as experimental. Are there particular features in the newer version that you're looking for? It should be straightforward for us to upgrade, but I don't see any rush at the moment. |
Also, if you are in a rush you can do the changes locally, test them and then report back. We have to err on the conservative side here. |
Thanks, to change locally I would have to re-compile/re-build the rblapi using the new version of Bloomberg api header files and dll. I checked that the new Bloomberg api header files differ from the old ones - meaning I probably have to change the rblapi source code as well.... |
Ideally, the new version will be backwards compatible and all the existing Rblpapi stuff will just work. But we don't know if that's the case until someone tries it. We would encourage you to try it and let us know what happens. |
hello, is there any update on the horizon? the new bloomberg api gives an opportunity to get ticks with milliseconds in timestamp. You can check this possibility in api demo tool. Is there any chance to get ticks with same miliseconds to R? Thanks for reply. |
I just pushed a branch "experimental" which builds with the newer version of the API 3.11.6.1. The package compiles but does not pass checks, so our previous suspicion is confirmed: there is more work to be done here. As always, code contributions are welcome. |
Hi,
So there are 2 issues:
I will keep investigating and see if I can fix it and submit an update. As worst we can just output the field as text and do the casting in R. thanks |
This is good and likely useful to somebody. Please open a new issue if you're able to make progress here or for further discussion. |
I made some progress, but need some advice because I am not that familiar with the In function
and that worked and I can see milliseconds in the data.frame output. Let me know if you see there is any issues in doing that. Or if there is a better way by keeping the |
I can help you there (even if I am without Bloomberg access these days). In very early days Rcpp may have imposed an int, it no longer does. Let's see if we can distill this into a small self-contained example to noodle over. But in essence package anytime does a lot around POSIXct. The 'newer' Datetime objects are also in RQuantLib and other places. We should be able to work with 'what we get' from Bbg -- if it is better than second we can surely pass it on. Bbg itself may have constraints from the exchanges and what not. |
Ok thank you, Let me see what I end up with. |
So for 2- trateTime we need to be using the newer API. The current supported one is v3.12.3.1. |
Quick question on Rblapi: the current version uses bloomberg blpapi
3.8.18.1; meanwhile bloomberg is asking people to upgrade to 3.11.6.1. Is
there any plan to release the updated version of Rblapi accordingly?
[Bloomberg did not give a drop dead date for 3.8.18.1 but they have been urging people to switch for a while]
thanks!
The text was updated successfully, but these errors were encountered: