Open mattrjacobs opened 8 years ago
This just came up today in a design where we started with using CompletableFuture and heavily rely on Hystrix. I am probably going to have to go back and use Futures now. Would be a nice feature.
Completely agree. I'm working on defining a clear roadmap and should be able to share that shortly. Please note that since CompletableFutures are Java8, this will have to wait until Hystrix 2.x, which will move to Java8.
The 2.0.x release seems to have become a bit stale. What is the current state of this project concerning java 8 migration? Just leaving this here for reference. :trollface:
Major Release | GA Date | End of Public Updates Notification | End of Public Updates |
---|---|---|---|
5.0 | May 2004 | Apr 2008 | Oct 2009 |
6 | Dec 2006 | Feb 2011 | Feb 2013 |
7 | Jul 2011 | Mar 2014 | Apr 2015 |
8 | Mar 2014 | TBD | Sep 2017* |
At the moment, there's no bandwidth available to work on this. Internally, we're shifting more of our resources to generating clients which have the same resiliency benefits of Hystrix while being polyglot.
@mattrjacobs any update this issue?
I'm definitely interested in this implementation as well. Any chance this could be implemented?
Any news for this?
Any update on this?
As soon as Hystrix targets JDK8 (as of now, Hystrix 2.0), how should we integrate
j.u.c.CompletableFuture
?AFAICT, it's better in all ways than
j.u.c.Future
. My inclination is to deprecatequeue()
and add a new method that returns aj.u.c.CompletableFuture
. I don't know what I would name this, however.Marked as 'discussion' as I'd love input on what makes sense here, design-wise.