-
Notifications
You must be signed in to change notification settings - Fork 476
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
How can I know errors like ConnectionTimeoutException in chunked query? #523
Comments
rhajek
added a commit
to bonitoo-io/influxdb-java
that referenced
this issue
Sep 26, 2018
rhajek
added a commit
to bonitoo-io/influxdb-java
that referenced
this issue
Sep 26, 2018
rhajek
added a commit
to bonitoo-io/influxdb-java
that referenced
this issue
Sep 26, 2018
rhajek
added a commit
to bonitoo-io/influxdb-java
that referenced
this issue
Sep 26, 2018
I think, this issue is a bug, there is no way how to handle this error. influxDB.query(query, chunksize,
//onNext result consumer
(cancellable, queryResult) -> {
System.out.println("Process queryResult - " + queryResult.toString());
}
//onComplete executable
, () -> {
System.out.println("On Complete - the query finished successfully.");
},
//onFailure error handler
throwable -> {
System.out.println("On Failure - " + throwable.getLocalizedMessage());
});
|
Get it. Thank you for the fixing. |
majst01
added a commit
that referenced
this issue
Sep 28, 2018
Fixed issue #523: onError handling for chunked queries
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I tried to execute a chunked query, it looks like no way to know about the query is failed because of errors like
ConnectionTimeoutException
. Since the chunked query is executed in an async way, my consumer cannot know about whether the query is finished or not so it can only keep waiting. Here is my code:I haved looked into the code of
influxdb-java
andokhttp3
. Ininfluxdb-java
, the failure callback do nothing but throw back the exception fromokhttp3
like this:And in
okhttp3
, for failure callback who also throws exception, it just print the stacktrace and finished. In this case, my consumer is not called at all and it looks no way to know about such failure in my code.The text was updated successfully, but these errors were encountered: