Paultagoras
Paultagoras
This is meant to be a detailed step-by-step guide to setting up the connector with an on-prem environment, going end-to-end.
It might be a good idea (if it's possible) to only store problematic records into the DLQ (so that mixed batches can mostly succeed).
The real question is do we WANT to lock it to java 8, or a later one - I remember we had the discussion, I just forget what the decision...
# Description We need to estimate the effort of migrating Kafka connector to the new client API. This issue is mainly about building a holistic view of a future work....
We should make sure the existing tests a) cover all of the different JDBC standards and b) are generic enough to not rely on specific client data types. ```[tasklist] ###...
The JDBC metadata should reflect the latest version of the client and ClickHouse, including transactions (or the lack thereof) ```[tasklist] ### Tasks - [ ] Any erroneous methods will be...
The various methods of the JDBC driver should utilize an instance of the V2 client, as well as V2 objects. ```[tasklist] ### Tasks - [ ] Any failing methods will...
This is the list of tests (with rough line numbers) that have been disabled, so we can revisit them and re-evaluate: - ClientIntegrationTest.java - (468, 34) testCompression - (2137, 34)...