We should write heavy hardcoded extensions of general interpretClient function for every ClickHouse HTTP interface usage patterns. And then use function interpretClient by specifying the extension.
Every extension of interpretClient function repeats injections of ClickHouse HTTP interface parts
ClickHouse HTTP interface usage patterns
Reading
Every reading process has the following general steps:
Client sends request with statement and auth data to a DBMS server
DBMS server handles statement and responses with the formatted data or an error message in http-body
The problems description
Right now we have an awkward library API for the ClickHouse HTTP Interface Which brings us to the next problems:
interpretClient
function for everyClickHouse HTTP interface
usage patterns. And then use functioninterpretClient
by specifying the extension.interpretClient
function repeats injections of ClickHouse HTTP interface partsClickHouse HTTP interface usage patterns
Reading
Every reading process has the following general steps:
statement
andauth data
to a DBMS serverformatted data
or anerror message
in http-bodyClient handles result of database response
Solutions