Allow points to be passed without explictly setting time or precision. It also fixes an issue with previopus implementation of the chunking support.
- #31: IndexOutOfRangeException thrown for partial writes
- #30: Use NanoSeconds as default precision
- Library will silently drop points older than retention period. This is similar to InfluDB behavios where it will reject those points with an
{"error":"partial write: points beyond retention policy dropped=225"}
This version adds Chunking support available in InfluxDB. Currently there is a open issue #8212 on Influxdb side, which is been handled with code, which needs to be removed once the issue is fixed.
- #28: Service Unavailable exception not thrown for unknown host
- #23: Chunking Support
QueryDBAsync
which was deprecated has been removed. Please useQueryMultiSeriesAsync
instead.
This version adds support for .Net Core.
- #17: Net Core Support
- Travis CI integration
Minor release to fix a blocking bug with data series with microsecond precision.
InfluxDBClient
now implementsIDispobale
, so plan to expect few warnings in your code. Similarly custom exceptions from this library are marked asSerializable
- #21: Microsecond precision data is stored as epoch 0
This version is a precursor to enable support for .Net Core. This restructures the solution folders, makes the unit tests truly independent of each other. It also supports deleting Continuous Queries. As of now it still does not support the .NBet Core as there are few open issues (e.g. #3199, #147) which are rooted in .Net Core's dependency on xproj
model. Once they move to csproj
these issues will be resolved, and this library will support .Net Core as well via .Net Standard (1.6+) PCL. Final goal is to have same set of source files, which gets complied as normal .Net 4.5 class library, and a PCL for the Core.
This version moves away from JavaScriptSerializer
to Json.NET. Functionally this is a transparent chnage. But this is required as former is not supported in .Net Core.
- #16: Create / Delete Continuous Query
- QueryMultiSeriesAsync returns the time in a
DateTime
object if the series has one. The method also supports different epoch precisoins in query results now.
QueryDBAsync
has been deprecated and will be removed in next version. Please useQueryMultiSeriesAsync
instead.
This version supports Continuous Queries. You can create a new CQ, or as well as query them. This version also has generic code changes to use new (well .Net 4.6 feature, so quite old) string interpolation syntax to remove String.Format("string {0}", interolatedValue)
instead use "$string{interolatedValue}"
.
Another change is to throw InfluxDBException
for any query failures. Before there were few cases where ArgumentException
was thrown.
- #16: Create Continuous Query
- #14: Regex for error extraction fails with type conflict errors. Thanks to @patHyatt for reporting and fixing it in #15
Updated to handle default auto generated retention policy name other than "default" #6586
This is a minor update to revert to using .Net 4.5.1. Previous version was changed to use .Net 4.6 by mistake.
This version supports Retention policies. You can create a new retention policy, or post into existing ones, as well as query them. This version also supports querying multi series data.
There is a breaking change to GetInfluxDBStructureAsync
, which now returns a custom InfluxDB object, which not only provides info about measurements, but also about tags and fields in each of them.
- #8: Add Nuget Package
- #10: Support for Retention Policy, query Influx Version
- #11: Enable AppVeyor integration for CI tests
Added type safe write methods via a new data structure called InfluxDataPoint. Previous write methods are marked obsolete.
Added the functionality to query for existing data from InfluxDB. Also unknown little quirk was Influx's need for . (dot) to treat a number as a number, so non US local code can beak Influx data writes. , now double to string conversion will work in any locale.
- #4: Add Querying InfluxDB functionality
- #3: Double to str conversion fix, Thanks to @spamik