Releases: InfluxCommunity/influxdb3-go
v2.8.0
Features
- #159: Support fast writes without waiting for WAL
persistence:- New write option (
WriteOptions.NoSync
) added:true
value means faster write but without the confirmation that
the data was persisted. Default value:false
. - Supported by self-managed InfluxDB 3 Core and Enterprise servers only!
- Also configurable via connection string query parameter (
writeNoSync
). - Also configurable via environment variable (
INFLUX_WRITE_NO_SYNC
). - Long precision string values added from v3 HTTP API:
"nanosecond"
,"microsecond"
,"millisecond"
,"second"
(
in addition to the existing"ns"
,"us"
,"ms"
,"s"
).
- New write option (
Bug Fixes
v2.7.0
Bug Fixes
- #158: Refactor Batcher and LPBatcher:
- Fields and methods using
capacity
renamed toinitialCapacity
. - Log messages when buffer data is not being emitted are simplified.
SetCapacity
methods on both structures are now deprecated.WithCapacity
andWithBufferCapacity
options are now deprecated.
- Fields and methods using
v2.6.0
2.5.0
Features
- #146: Add error field to QueryIterator to hold first possible error encountered when retrieving records from the flight Reader.
- #147: Ability to pass
grpc.CallOption
functions to the underlying flight Client. - #149: Add default configuration for the built-in HTTP
client and expose new configurable parameters:Timeout
- The overall time limit for requests made by the Client. A negative value means no timeout. Default
value: 10 seconds.IdleConnectionTimeout
- Maximum time an idle connection will remain idle before closing itself. A negative value
means no timeout. Default value: 90 seconds.MaxIdleConnections
- Maximum number of idle connections. It sets bothtransport.MaxIdleConn
and
transport.MaxIdleConnsPerHost
to the same value. A negative value means no limit. Default value: 100.
- #154: Export functions
NewQueryIterator
and
NewPointValueIterator
to simplify testing.
v2.4.0
v2.3.0
Features
- #131: Add new PointValueIterator based on google
guidelines Guidelines
2.2.0
2.1.0
2.0.0
2.0.0 [2024-12-13]
Breaking Changes
Previously, the Query API did not respect the metadata type for columns returned from InfluxDB v3. This release fixes this issue. As a result, the type of some columns may differ from previous versions. For example, the timestamp column will now be
time.Time
instead ofarrow.Timestamp
.
Update steps:
- Update library:
go get github.com/InfluxCommunity/influxdb3-go/v2/influxdb3
- Update import path in Go files to
github.com/InfluxCommunity/influxdb3-go/v2/influxdb3
.
Features
- #114: Query API respects metadata types for columns returned from InfluxDB v3.
Tags are mapped as a "string", timestamp as "time.Time", and fields as their respective types:- iox::column_type::field::integer: => int64
- iox::column_type::field::uinteger: => uint64
- iox::column_type::field::float: => float64
- iox::column_type::field::string: => string
- iox::column_type::field::boolean: => bool
v1.0.0
Breaking Changes
Previously, the Query API did not respect the metadata type for columns returned from InfluxDB v3. This release fixes this issue. As a result, the type of some columns may differ from previous versions. For example, the timestamp column will now be
time.Time
instead ofarrow.Timestamp
.
Features
- #114: Query API respects metadata types for columns returned from InfluxDB v3.
Tags are mapped as a "string", timestamp as "time.Time", and fields as their respective types:- iox::column_type::field::integer: => int64
- iox::column_type::field::uinteger: => uint64
- iox::column_type::field::float: => float64
- iox::column_type::field::string: => string
- iox::column_type::field::boolean: => bool