Group: GitHub Orhaugh

Sort by:Popular▼

✓Popular✓Newest

ClickHouse native TCP protocol model: packet identifiers, protocol revisions and feature gates, handshake structures, wire primitives, the connection state machine and the CHord exception hierarchy. This module has no runtime dependencies.

Reusable test fixtures for CHord and downstream consumers: a Testcontainers ClickHouse fixture with native TCP exposure and deterministic credentials. This module deliberately depends on no other CHord module so client tests can use it ...

The CHord client API. At this stage it provides the low-level NativeConnection covering handshake, authentication and ping.

The ClickHouse type model and type name parser, primitive columnar values, column codecs and native block decoding. Compression frames arrive in Phase 4; LowCardinality, Variant, Dynamic and JSON decoding in Phase 6.

Blocking TCP and TLS transports for the ClickHouse native protocol: socket configuration, connect and read deadlines, always-on hostname verification, mutual TLS, and the transport SPI behind which future transports sit.

Bill of materials aligning the versions of all CHord modules.

JDBC 4.3 adapter over the CHord native client: Driver, Connection, Statement, PreparedStatement with native block batching, ResultSet, DatabaseMetaData and DataSource. Features ClickHouse does not have raise SQLFeatureNotSupportedException ...

Optional Micrometer integration for CHord: connection pool metrics binding. Per operation timing is provided by the JFR events built into chord-client.

CHord is a Java client for ClickHouse built on the ClickHouse native TCP wire protocol. This is the parent build for all CHord modules.