Lucas Kent
Lucas Kent
- [x] Tested on all platforms changed - [x] Added an entry to `CHANGELOG.md` if knowledge of this change could be valuable to users - [x] Updated documentation to reflect...
Another issue arising from discussion in the rust community discord. Panicking over FFI boundaries is UB, so we should wrap every extern C function with catch_unwind. Ideally the rust API...
Value::Number should be changed from a tuple variant to a struct variant so that the field names are self documenting. Something like: `Number { value: String, long: bool }` Possibly...
Not even compiling yet, just demonstrating the direction of the fix.
`cluster_sink_rack_single` is duplicated into `cluster_sink_rack_single_v3` and `cluster_sink_rack_single_v4` To support this we split off the version specific parts from `cassandra_int_tests/cluster.rs` into `cassandra_int_tests/cluster_single_rack_v3.rs` and `cassandra_int_tests/cluster_single_rack_v4.rs` Every other int test can be swapped...
Returning an error for WHERE on system.peers makes complete sense to me as we currently make no attempt to handle the WHERE and I havent seen drivers use a WHERE...
Currently we hardcode the port 9042 everywhere, but we should handle the port dynamically from the config and system.peers_v2 results.
I think some are due to configuration errors and others are due to CassandraSinkCluster confusing it.
* system_schema queries should go through the control connection * tracing queries should be rejected
This error can be seen in some cassandra integration tests (or at least it will be once https://github.com/shotover/shotover-proxy/pull/765 lands) I believe it indicates we are doing something weird with connections,...