-
Notifications
You must be signed in to change notification settings - Fork 186
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
Scala 2.13 Reactive/Akka Streams #926
Comments
I have a naive implementation here that we're starting with. the main issue I have is I'm not sure how we can avoid the blocking calls. I was having a play with some system where it makes non-blocking calls when the buffer is below a certain level but a) More than one request in flight and we risk adding to the buffer out of order and/or screwing with the page state on the next call. For now this is with Akka Streams but if it's not completely dumb It could probably be done with reactivestreams as a Publisher and then Akka can build from that itself.
This can then be called with
|
Hi there.
What was the status of the reactive streams connector for Scala 2.13? From reading the docs there was a dependency issue? I am working on a system where we have to load a load of data into a cluster and then I need to dump it back out. For now I will be create a Source with Akka streams and pagination (or some flavour of this) to get things moving but if there is work already existing maybe I could see If what I work on could be generalised and added in a PR to return a table Model as a reactive Publisher (and maybe a source too?)? I know I'd prefer it if I can roll some sort of reactive interface into phantom rather than managing our own or having both phantom and alpakka dependencies and their own dependencies on datastax connector. I'm a little intimidated by the macros and reflection aspects to Phantom but I'm not sure how much I'd need to touch that for creating a Source from pagination.
Thanks so much for all the work on Phantom.
All the Best
The text was updated successfully, but these errors were encountered: