Martin Sucha

Unfortunately, it seems that changing usage of `TypeInfo` family of types to pointer receiver is a backward incompatible change, so it would need to be in a new major version....

There are no concrete plans for v2 now. There are other things that require breaking changes and should be included in v2. Some of those other things are marked with...

@nkev Personally I don't plan to work on Cassandra 5 support, if anyone else wants to, feel free. See [a more detailed response in the mailing list](https://groups.google.com/g/gocql/c/v0FruczBb2w/m/KBso2NfJAQAJ).

I don't think it's safe to reuse the tokenaware policy between sessions even if you fix this race.

Do you see a panic or is there something else that causes the stack trace to be printed? > github.com/gocql/gocql v0.0.0-20191102131523 This version seems to be old and seems to...

See my reply at https://github.com/gocql/gocql/issues/1596#issuecomment-1037015708

Looks good to me. The same issue is present upstream in https://github.com/gocql/gocql, maybe you could open a pull request there directly? I'd be happy to merge it there.

Do you want to support named query parameters (e.g. `SELECT * FROM table where a = :a and b = :b`) or do you want to ignore the named parameters...

Yep, I'm not aware of any public API to determine which node (resp. in case of Scylla you would group by shard) the partition key maps to. We just split...

Nice! I was thinking whether using ShuffleHosts or similar could cause problems, but even if the host selection policy picks a non-primary replica, the Scylla node should still have all...