Moving data from BigQuary to Clickhouse

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu server
  • Memory / Disk: 16gb, 1 tb
  • Deployment: Docker
  • Airbyte Version: 0.36.11-alpha
  • Source name/version: BigQuery (0.1.7)
  • Destination name/version: Clickhouse (0.1.5)
  • Step: Downloading normalization data
  • Description: There was a problem at the stage of moving data from BigQuary to Clickhouse.
    The raw data moved without much problem. But there was a problem with automatic normalization

maybe helpfull
“2022-05-06 05:53:43 normalization > Code: 102. Unexpected packet from server (expected Hello or Exception, got Unknown packet)
2022-05-06 05:53:43 normalization >
2022-05-06 05:53:43 normalization > Check your database credentials and try again. For more information, visit:
2022-05-06 05:53:43 normalization > Configuring your profile | dbt Docs
2022-05-06 05:53:43 normalization >
2022-05-06 05:53:43 normalization >
2022-05-06 05:53:43 INFO i.a.w.t.TemporalAttemptExecution(lambda$getWorkerThread$2):161 - Completing future exceptionally…
io.airbyte.workers.WorkerException: Normalization Failed.”

logs-17829-1 (1).txt (22.7 KB)

Also i did the same connection before between BQ → Postrgess and that was working correct with normalization

Hey @Vaitar,
Could you please upgrade your Airbyte version to the latest one (>= 0.38.0)?
It looks like the normalization image for Clickhouse (0.1.61) was not published or does not exist anymore.
If you upgrade Airbyte to a newer version your error will probably be fixed.

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.