-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(outputs.sql): Update ClickHouse Docker image for integration test #16462
chore(outputs.sql): Update ClickHouse Docker image for integration test #16462
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AndreKR thanks for the PR. Just one comment...
85016bb
to
c86f67f
Compare
The Docker image `yandex/clickhouse-server` that has been used for the integration test hasn't been updated in 3 years. ClickHouse has moved to the Docker image that is called `clickhouse`. This uses the new image for the integration test. The log messages have changed, so that is taken into account when waiting for the test container to spin up. Technically waiting for the open port would be enough but for good measure we also wait for a corresponding log output. To get the log output, a config file is included.
c86f67f
to
a4d3e5d
Compare
Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @AndreKR!
Summary
The Docker image
yandex/clickhouse-server
that has been used for the integration test hasn't been updated in 3 years. ClickHouse has moved to the Docker image that is calledclickhouse
.This uses the new image for the integration test.
The log messages have changed, so that is taken into account when waiting for the test container to spin up. Technically waiting for the open port would be enough but for good measure we also wait for a corresponding log output. To get the log output, a config file is included.
Checklist
Related issues
resolves #16461