Releases · questdb/go-questdb-client

Add support for the ILP protocol over HTTP transport, as well as the new config string syntax #26
- The new HTTP sender has better error reporting. In particular, it returns an error if the QuestDB server failed to write ILP messages for any reason.
- HTTP sender handles network errors and retries writes automatically.
- HTTP sender reuses connections to avoid open connection overhead for each Flush call.
- The new LineSenderFromConf method provides a convenient way for creating a LineSender based on a config string.

Migration

v2 code example:

package main import ( "context"	qdb "github.com/questdb/go-questdb-client/v2" ) func main() { // Connect to QuestDB running on 127.0.0.1:9009 (ILP/TCP) sender, err := qdb.NewLineSender(context.TODO()) // ... defer sender.Close() // ... }

Migrated v3 code:

package main import ( "context"	qdb "github.com/questdb/go-questdb-client/v3" ) func main() { // Connect to QuestDB running on 127.0.0.1:9000 (ILP/HTTP) sender, err := qdb.NewLineSender(context.TODO(), qdb.WithHTTP()) // Alternatively, you can use the LineSenderFromConf function: // sender, err := qdb.LineSenderFromConf(ctx, "http::addr=localhost:9000;") // ... defer sender.Close(context.TODO()) // ... }

Note that the migrated code uses the HTTP sender instead of the TCP one.

Assets 2

10 Oct 09:16

puzpuzpuz

v2.0.0

e8d780a

2.0.0

Release overview

Maintenance release to include important API improvements.

What is new

Introduce safer timestamp API #23
- All timestamp methods now require time.Time type instead of int64. This is a breaking change, so the old code will have to be updated. To use the new client, you need to import github.com/questdb/go-questdb-client/v2 instead of the old github.com/questdb/go-questdb-client path.
Fix godoc for WithTlsInsecureSkipVerify #19