cql-proxy
cql-proxy copied to clipboard
datastax
A client-side CQL proxy/sidecar.
I think is safe to move to Go 1.18 and remove Go 1.16 and 1.15 from CI. This will allow for simplification of a couple places in the code and...
For now the goal would just be to have pre-built binaries available for download with each release. In the future it would be nice to have something more robust. One...
It would be a security improvement if clients could be made to authenticate optionally, based on a flag provided when the proxy started up. Something like `--client-auth`, which then causes...
So when a client connects, could it authenticate a new connection for that client using the client's Astra username and password? Then use that connection to make all the requests...
In our testing we have a process where we test our application's binary as it goes to production. For HTTP we use contracts to stub data and we use fault...
IHAC that ran into an issue with what looks like a dependency issue in go-cassandra-native-protocol: ``` # github.com/datastax/cql-proxy/parser /go/pkg/mod/github.com/datastax/[email protected]/parser/metadata.go:28:71: undefined: datatype.NewSetType /go/pkg/mod/github.com/datastax/[email protected]/parser/metadata.go:46:71: undefined: datatype.NewSetType /go/pkg/mod/github.com/datastax/[email protected]/parser/metadata.go:61:71: undefined: datatype.NewSetType /go/pkg/mod/github.com/datastax/[email protected]/parser/metadata.go:73:71: undefined: datatype.NewSetType...
Consider pulling [Astra SCB logic](https://github.com/datastax/cql-proxy/blob/main/astra/bundle.go) in cql-proxy into a free-standing library. This library could be managed and versioned separately from cql-proxy proper and could provide an API for the following...
This case leads to the following error message: ``` {"level":"error","ts":1674158444.9508557,"caller":"proxycore/cluster.go:357","msg":"unable to create new endpoint","error":"ignoring host because its `peer` is not set or is invalid","stacktrace": "github.com/datastax/cql-proxy/proxycore.(*Cluster).addHosts\n\t/go/src/cql-proxy/proxycore/cluster.go:357 github.com/datastax/cql-proxy/proxycore.(*Cluster).queryHosts\n\t/go/src/cql-proxy/proxycore/cluster.go:300 github.com/datastax/cql-proxy/proxycore.(*Cluster).connect\n\t/go/src/cql-proxy/proxycore/cluster.go:223 github.com/datatax/cql-proxy/proxycore.ConnectCluster\n\t/go/src/cql-proxy/proxycore/cluster.go:163 github.com/datastax/cql-proxy/proxy.(*Proxy).Connect\n\t/go/src/cql-proxy/proxy/proxy.go:167 github.com/datastax/cql-proxy/proxy.(*runConfig).listenAndServe\n\t/go/src/cql-proxy/proxy/run.go:274...
This pull request fixes the issue where the `SetKeyspaceResult` in the response message of the `USE` statement does not reflect the actual keyspace name. Previously, when using the `USE` statement...
