You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I have two databases, we shall call them default and newdb containing identical tables, and if I connect to clickhouse directly using http://username:password@localhost:8123/default or http://username:password@localhost:8123/newdb I am able to submit queries to the correct database.
However, with clickhouse-bulk, the exact same connection strings as above, inserts to both databases are aggregated into the same DB.
I can (and am now) running a copy of clickhouse-bulk per database, but this seems sub-optimal. Absolute minimum case, clickhouse-bulk should reject queries sent to /newdb if it is only going to insert into a single DB.
The text was updated successfully, but these errors were encountered:
I've tried to work around this in a number of ways.
Specifying the server to clickhouse-bulk pushes to, has zero effect (it always inserts into default) - so running multiple instances doesn't work
Including the database name in the table name (e.g. INSERT INTO newdb.accounts VALUES (...) means the http requests are accepted by clikchouse-bulk (no errors, in logs or response) but nothing is ever flushed to the upstream server
So I have two databases, we shall call them
default
andnewdb
containing identical tables, and if I connect to clickhouse directly usinghttp://username:password@localhost:8123/default
orhttp://username:password@localhost:8123/newdb
I am able to submit queries to the correct database.However, with clickhouse-bulk, the exact same connection strings as above, inserts to both databases are aggregated into the same DB.
I can (and am now) running a copy of clickhouse-bulk per database, but this seems sub-optimal. Absolute minimum case, clickhouse-bulk should reject queries sent to
/newdb
if it is only going to insert into a single DB.The text was updated successfully, but these errors were encountered: