thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-11-16 20:53:27 +00:00
Code Issues Packages Projects Releases Wiki Activity
0336a4ad58
ClickHouse/programs/odbc-bridge
History
Vitaly Baranov 4733504b51 Don't split dictionary source's table name into schema and table name itself 
if ODBC driver doesn't support schema.
2020-07-06 23:41:39 +03:00
..
tests
CMakeLists.txt Don't split dictionary source's table name into schema and table name itself 2020-07-06 23:41:39 +03:00
ColumnInfoHandler.cpp Return old names of macros 2020-05-24 01:24:01 +03:00
ColumnInfoHandler.h
getIdentifierQuote.cpp
getIdentifierQuote.h
HandlerFactory.cpp Don't split dictionary source's table name into schema and table name itself 2020-07-06 23:41:39 +03:00
HandlerFactory.h Don't split dictionary source's table name into schema and table name itself 2020-07-06 23:41:39 +03:00
IdentifierQuoteHandler.cpp Return old names of macros 2020-05-24 01:24:01 +03:00
IdentifierQuoteHandler.h
MainHandler.cpp Return old names of macros 2020-05-24 01:24:01 +03:00
MainHandler.h
odbc-bridge.cpp
ODBCBlockInputStream.cpp Remove namespace pollution 2020-05-31 00:57:37 +03:00
ODBCBlockInputStream.h
ODBCBlockOutputStream.cpp Remove namespace pollution 2020-05-31 00:57:37 +03:00
ODBCBlockOutputStream.h
ODBCBridge.cpp Return old names of macros 2020-05-24 01:24:01 +03:00
ODBCBridge.h
PingHandler.cpp
PingHandler.h
README.md
SchemaAllowedHandler.cpp Don't split dictionary source's table name into schema and table name itself 2020-07-06 23:41:39 +03:00
SchemaAllowedHandler.h Don't split dictionary source's table name into schema and table name itself 2020-07-06 23:41:39 +03:00
validateODBCConnectionString.cpp Slightly loose the validation of ODBC connection string 2020-06-21 20:28:40 +03:00
validateODBCConnectionString.h

README.md

clickhouse-odbc-bridge

Simple HTTP-server which works like a proxy for ODBC driver. The main motivation was possible segfaults or another faults in ODBC implementations, which can crash whole clickhouse-server process.

This tool works via HTTP, not via pipes, shared memory, or TCP because:

  • It's simpler to implement
  • It's simpler to debug
  • jdbc-bridge can be implemented in the same way

Usage

clickhouse-server use this tool inside odbc table function and StorageODBC. However it can be used as standalone tool from command line with the following parameters in POST-request URL:

  • connection_string -- ODBC connection string.
  • columns -- columns in ClickHouse NamesAndTypesList format, name in backticks, type as string. Name and type are space separated, rows separated with newline.
  • max_block_size -- optional parameter, sets maximum size of single block. Query is send in post body. Response is returned in RowBinary format.

Example:

$ clickhouse-odbc-bridge --http-port 9018 --daemon

$ curl -d "query=SELECT PageID, ImpID, AdType FROM Keys ORDER BY PageID, ImpID" --data-urlencode "connection_string=DSN=ClickHouse;DATABASE=stat" --data-urlencode "columns=columns format version: 1
3 columns:
\`PageID\` String
\`ImpID\` String
\`AdType\` String
"  "http://localhost:9018/" > result.txt

$ cat result.txt
12246623837185725195925621517