-
Notifications
You must be signed in to change notification settings - Fork 41
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
Fix #82: QueryMultiSeriesAsync should return "partial" #85
Conversation
…ponses are truncated by InfluxDB
The checks are failing because InfluxDB needs a special configuration for a new test to succeed (or we could remove the test, but I think it would be better to explicitly test the new functionality). |
[skip ci]
…Result Support multi query with multi result
Added PostQuery.
* Added PostQuery. * Added constructor.
You seems to be busy coding.. Thank you for your contribution. I am stuck with work and personal stuff.. I will probably review this over weekend. |
Hi @mvadu sorry, we did not know that all the changes in our fork would be included in this PR, this was not our intention... I'll reopen another pull request. Please ignore this one and sorry for the circumstances... |
@tbraun-hk are you going submit the partial flag part of this PR? |
Hi @mvadu yes, you are right. Sorry for taking so long, I'll open another pull request in the next couple of days. |
This pull request is an attempt to implement #82
If InfluxDB is configured to have a "max-row-limit", then InfluxDB will return the flag "partial=true" to indicate that a response has been truncated due to the max-row-limit.
With this pull request, the "partial" flag is included in the IInfluxSeries and set according to the influx raw response.
A unit test that verifies the changes has been implemented, too. However, you need to have an InfluxDB system with max-row-limit set to 100.000 for this test to succeed.