You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry if this is a dumb question, I am a beginner in InfluxDB and this library. I would like to invoke it for a high volume of input coming from a Java application. That application will use RxJava / Reactive Streams all the way, so it is completely non-blocking.
Is it supported at all? Any pointers to a possible wrapping of the current calls so that they are observables or equivalent?
The text was updated successfully, but these errors were encountered:
dfernandezm
changed the title
Support for Reactive streams / RxJava integration or non-blocking alternative
Question: Any support for Reactive streams / RxJava integration or non-blocking alternative?
Dec 4, 2017
@dfernandezm IMO there is a feasible approach for reactive streams with the current API. However it's important to notice that it may not be the best solution and the API will probably be rewritten soon (for a more complete overview about existing issues, check this document).
I'm assuming that you want to write as may points in one HTTP call as possible. So I would:
Enable the batch mode (org.influxdb.impl.InfluxDBImpl.enableBatch(int, int, TimeUnit, ThreadFactory, BiConsumer<Iterable<Point>, Throwable>));
Create a BiConsumer to notify my Observable for errors. Currently we don't have a way to notify on successful writes (this issue is mentioned on the document).
BTW, any contribution here (e.g. a refactoring to support CompletableFuture or another approach that do not add external dependencies) would be great! :)
Hi all,
Sorry if this is a dumb question, I am a beginner in InfluxDB and this library. I would like to invoke it for a high volume of input coming from a Java application. That application will use RxJava / Reactive Streams all the way, so it is completely non-blocking.
Is it supported at all? Any pointers to a possible wrapping of the current calls so that they are observables or equivalent?
The text was updated successfully, but these errors were encountered: