| commit | 4367d090becb1a32ec585e539e70e62e5235594e | [log] [tgz] |
|---|---|---|
| author | Martin Sucha <martin.sucha@kiwi.com> | Wed Apr 26 15:42:48 2023 +0200 |
| committer | Martin Sucha <martin.sucha@kiwi.com> | Wed Apr 26 15:42:48 2023 +0200 |
| tree | 558d6715664ba83ca5908e35bed8b4ee7d03e94f | |
| parent | 4aa611938859ea90190c6f36ebf9a7957be5d690 [diff] |
Update changelog for 1.4.0
Package gocql implements a fast and robust Cassandra client for the Go programming language.
Project Website: https://gocql.github.io/
API documentation: https://godoc.org/github.com/gocql/gocql
Discussions: https://groups.google.com/forum/#!forum/gocql
The following matrix shows the versions of Go and Cassandra that are tested with the integration test suite as part of the CI build:
| Go/Cassandra | 4.0.x | 4.1.x |
|---|---|---|
| 1.19 | yes | yes |
| 1.20 | yes | yes |
Gocql has been tested in production against many versions of Cassandra. Due to limits in our CI setup we only test against the latest 2 GA releases.
In general, the gocql team will focus on supporting the current and previous versions of Go. gocql may still work with older versions of Go, but official support for these versions will have been sunset.
go get github.com/gocql/gocql
Marshaler and Unmarshaler interfaceWhile the driver strives to be highly performant, there are cases where it is difficult to test and verify. The driver is built with maintainability and code readability in mind first and then performance and features, as such every now and then performance may degrade, if this occurs please report and issue and it will be looked at and remedied. The only time the driver copies data from its read buffer is when it Unmarshal's data into supplied types.
Some tips for getting more performance from the driver:
GOGCgocql no longer supports executing “use ” statements to simplify the library. The user still has the ability to define the default keyspace for connections but now the keyspace can only be defined before a session is created. Queries can still access keyspaces by indicating the keyspace in the query:
SELECT * FROM example2.table;
Example of correct usage:
cluster := gocql.NewCluster("192.168.1.1", "192.168.1.2", "192.168.1.3")
cluster.Keyspace = "example"
...
session, err := cluster.CreateSession()
Example of incorrect usage:
cluster := gocql.NewCluster("192.168.1.1", "192.168.1.2", "192.168.1.3")
cluster.Keyspace = "example"
...
session, err := cluster.CreateSession()
if err = session.Query("use example2").Exec(); err != nil {
log.Fatal(err)
}
This will result in an err being returned from the session.Query line as the user is trying to execute a “use” statement.
There are various ways to bind application level data structures to CQL statements:
[]map[string]interface{} using the SliceMap() API. This returns a slice of row maps keyed by CQL column names. This method requires no special interaction with the gocql API, but it does require your application to be able to deal with a key value view of your data.SliceMap() API you can also call MapScan() which returns map[string]interface{} instances in a row by row fashion.Bind() API provides a client app with a low level mechanism to introspect query meta data and extract appropriate field values from application level data structures.The following community maintained tools are known to integrate with gocql:
database/sql package. This project isn’t maintained anymore, because Cassandra wasn't a good fit for the traditional database/sql API. Use this package instead.For some reason, when you Google golang cassandra, this project doesn‘t feature very highly in the result list. But if you Google go cassandra, then we’re a bit higher up the list. So this is note to try to convince Google that golang is an alias for Go.
Copyright (c) 2012-2016 The gocql Authors. All rights reserved. Use of this source code is governed by a BSD-style license that can be found in the LICENSE file.