go-questdb-client icon indicating copy to clipboard operation
go-questdb-client copied to clipboard

Golang client for QuestDB's Influx Line Protocol

Results 11 go-questdb-client issues
Sort by recently updated
recently updated
newest added
trafficstars

This sample is a bit silly: https://github.com/questdb/go-questdb-client/blob/2190485745fb270465fabf6af364bcb7dee3b61a/examples/from-conf/main.go I assume this was taken from Java samples which I am guilty of using in the past. We should use samples related to...

enhancement

See https://github.com/questdb/questdb/pull/4385/

enhancement

It looks like the go client doesn't support something like `BinaryColumn`, which is [supported by the core db](https://questdb.io/docs/reference/sql/datatypes/). But it looks like the [ILP parser doesn't support binary types](https://github.com/questdb/questdb/blob/master/core/src/main/java/io/questdb/cutlass/line/tcp/LineTcpParser.java) yet...

enhancement

Hi, thanks for your library and awesome db! I generate line protocol entry via reflection and I got all my lines ready to be pushed. I want to use the...

It would be nice to have something like https://pkg.go.dev/github.com/jackc/pgx/v5/pgxpool so we could instantiate a pool of senders to be concurrently reused across go routines.

Because LineSenders are meant to be single-threaded, this PR introduces a LineSenderPool that makes it easier to achieve greater throughput with multiple concurrent senders

See this test run: https://github.com/questdb/go-questdb-client/actions/runs/10168945531 Tests failed because: ``` integration_test.go:427: Error Trace: /home/runner/work/go-questdb-client/go-questdb-client/integration_test.go:427 Error: Received unexpected error: Error response from daemon: network with name test-network-v3 already exists: failed to create...

An http `/ping` endpoint is implemented in the database, but not included in this client. Ping can be useful for testing connection strings before attempting to send data over the...

I hit [this issue](https://github.com/haproxy/haproxy/issues/2043) when running unit tests locally. This PR adds a global maxconn and bumps haproxy from 2.6.0 -> 2.6.4 to prevent the issue.

Changed README, examples, and a minor comment so the examples are consistent across different client libs and the demo site