mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-12-17 20:02:05 +00:00
dbfb448290
There is logic regarding which keeper binary use to start keeper cluster in an integration test There 2 options: (1) standalone keeper binary (expected binary name clickhouse-keeper) (2) clickhouse binary with keeper inside Fixed: - option (1) didn't work since docker_compose_keeper.yaml didn't create target clickhouse-keeper at all - if clickhouse-keeper existed, option (1) was taken but clickhouse-keeper could be just a link to clickhouse binary (the link is created always during build if cmake option BUILD_STANDALONE_KEEPER is OFF) |
||
|---|---|---|
| .. | ||
| docker_compose_azurite.yml | ||
| docker_compose_cassandra.yml | ||
| docker_compose_coredns.yml | ||
| docker_compose_dotnet_client.yml | ||
| docker_compose_hdfs.yml | ||
| docker_compose_hive.yml | ||
| docker_compose_jdbc_bridge.yml | ||
| docker_compose_kafka.yml | ||
| docker_compose_keeper.yml | ||
| docker_compose_kerberized_hdfs.yml | ||
| docker_compose_kerberized_kafka.yml | ||
| docker_compose_meili.yml | ||
| docker_compose_minio.yml | ||
| docker_compose_mongo_secure.yml | ||
| docker_compose_mongo.yml | ||
| docker_compose_mysql_5_7_for_materialized_mysql.yml | ||
| docker_compose_mysql_8_0.yml | ||
| docker_compose_mysql_client.yml | ||
| docker_compose_mysql_cluster.yml | ||
| docker_compose_mysql_golang_client.yml | ||
| docker_compose_mysql_java_client.yml | ||
| docker_compose_mysql_js_client.yml | ||
| docker_compose_mysql_php_client.yml | ||
| docker_compose_mysql.yml | ||
| docker_compose_nats.yml | ||
| docker_compose_net.yml | ||
| docker_compose_nginx.yml | ||
| docker_compose_postgres_cluster.yml | ||
| docker_compose_postgres.yml | ||
| docker_compose_postgresql_java_client.yml | ||
| docker_compose_postgresql.yml | ||
| docker_compose_rabbitmq.yml | ||
| docker_compose_redis.yml | ||
| docker_compose_zookeeper_secure.yml | ||
| docker_compose_zookeeper.yml | ||