Michael Penick

Hey, I think domain name verification is working as intended. The driver uses reverse DNS to lookup the name for certificate validation (which is a side effect of Cassandra using...

Thanks for the operators. I'd prefer these live in a C++ specific header and could you add some tests?

* Make sure that the existing CQL integration tests work with the java-driver using protocol v5 * Explicitly test that the result metadata ID stuff works with all the backends...

This is somewhat nontrivial because protocol-level checksumming resulted in a large refactor to the framing/messaging code.

Stargate currently only supports protocol v3, v4 and v5-beta. The CQL native transport protocol was updated in Cassandra 4.0 to include protocol v5. However, the v5-beta version in previous versions,...

``` * Added result set metadata id to Prepared responses (Section 4.2.5.4) ``` The `` change is also likely to require some amount of integration with the `Persistence` layer to...

@jeffreyscarpenter @maheshrajamani I was thinking more about this. We might also need to also spoof the `system.peers_v2` table in Stargate to fully support protocol v5. It's an implicit requirement for...

Internally, the other connections would need to connect using `metadata.ContactInfo.SniProxyAddress` + the `host_id` (from the system tables) as the SNI servername.

Thanks for the heads up. I can take a look today at a fix that doesn't break TLS.

Pushed up another fix that keeps the original hostname used in the contact points. It should be noted that hosts discovered through the peers table won't have valid hostnames because...