Skip to content

fix: query error could be after "success" table#173

Merged
bednar merged 4 commits intomasterfrom
fix/query-error-in-next-table
Nov 11, 2020
Merged

fix: query error could be after "success" table#173
bednar merged 4 commits intomasterfrom
fix/query-error-in-next-table

Conversation

@bednar
Copy link
Copy Markdown
Contributor

@bednar bednar commented Nov 9, 2020

Closes #171

Proposed Changes

According to specification of Flux, the error could be propagated after "success" table:

When an error occurs after some results have already been sent to the client the error will be encoded as the next table and the rest of the results will be discarded. In such a case the HTTP status code cannot be changed and will remain as 200 OK.

https://github.com/influxdata/flux/blob/master/docs/SPEC.md#errors

Checklist

  • CHANGELOG.md updated
  • Rebased/mergeable
  • A test has been added if appropriate
  • mvn test completes successfully
  • Commit messages are in semantic format
  • Sign CLA (if not already signed)

@bednar bednar merged commit 5e9c859 into master Nov 11, 2020
@bednar bednar deleted the fix/query-error-in-next-table branch November 11, 2020 09:28
@bednar bednar added this to the 1.14.0 milestone Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

com.influxdb.exceptions.InfluxException: For input string: "",when reciving error from influxdb

2 participants