Closed LPauzies closed 2 months ago
The 9440 port you listed in your <remote_servers>
is the native "secure" port. You either need to use <secure>1</secure>
in the <replica>
configuration or use the "non-secure" port that is configured on your ClickHouse server (since you apparently moved it from 9000 to something else due to an nginx conflict?). See https://clickhouse.com/docs/en/engines/table-engines/special/distributed.
In any case, this is not a specific DBT problem -- you should be able to test your access to your cluster just using the ClickHouse Client.
Describe the bug
I'm building a ClickHouse cluster and for testing purpose, we will need to have the same number of topologies in a dev environment to mimic the production.
When I try running DBT in my remote dev server I got this message in my clickhouse logs :
Here is the message I got when I'm running it on my local against remote server :
Here is the cluster.xml
Here is the profile.yml I would use :
Here is the dbt_project.yml :
My CH cluster is on a remote server, from which i'm ssh tunneling it. The native port is forwarded on 9433. The connection is going well when I go to the server and log into it using my credentials.
Expected behavior
Running
dbt run --target dev-profile --project-dir ./transform_dbt --profiles-dir ./transform_dbt
should work the same way I did in local with a docker compose setup.Here is my
dbt-debug
:Configuration
Environment
ClickHouse server
What do you think about this ? Do I open the same issue into ClickHouse repository ?
Thanks for reading me and for your time :pray: