thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-12-04 05:22:17 +00:00
Code Issues Packages Projects Releases Wiki Activity
47966c4e81
ClickHouse/tests/config
History
何李夫 e4c8c4cecf
Add zookeeper name in endpoint id (#49780) 
* Add zookeeper name in endpoint id

When we migrate a replicated table from one zookeeper cluster to
another (the reason why we migration is that zookeeper's load is
too high), we will create a new table with the same zpath, but it
will fail and the old table will be in trouble.

Here is some infomation:
1.old table:
  CREATE TABLE a1 (`id` UInt64)
  ENGINE = ReplicatedMergeTree('/clickhouse/tables/default/a1/{shard}', '{replica}')
  ORDER BY (id);
2.new table:
  CREATE TABLE a2 (`id` UInt64)
  ENGINE = ReplicatedMergeTree('aux1:/clickhouse/tables/default/a1/{shard}', '{replica}')
  ORDER BY (id);
3.error info:
  <Error> executeQuery: Code: 220. DB::Exception: Duplicate interserver IO endpoint:
          DataPartsExchange:/clickhouse/tables/default/a1/01/replicas/02.
          (DUPLICATE_INTERSERVER_IO_ENDPOINT)
  <Error> InterserverIOHTTPHandler: Code: 221. DB::Exception: No interserver IO endpoint
          named DataPartsExchange:/clickhouse/tables/default/a1/01/replicas/02.
          (NO_SUCH_INTERSERVER_IO_ENDPOINT)

* Revert "Add zookeeper name in endpoint id"

This reverts commit 9deb75b249619b7abdd38e3949ca8b3a76c9df8e.

* Add zookeeper name in endpoint id

When we migrate a replicated table from one zookeeper cluster to
another (the reason why we migration is that zookeeper's load is
too high), we will create a new table with the same zpath, but it
will fail and the old table will be in trouble.

* Fix incompatible with a new setting

* add a test, fix other issues

* Update 02442_auxiliary_zookeeper_endpoint_id.sql

* Update 02735_system_zookeeper_connection.reference

* Update 02735_system_zookeeper_connection.sql

* Update run.sh

* Remove the 'no-fasttest' tag

* Update 02442_auxiliary_zookeeper_endpoint_id.sql

---------

Co-authored-by: Alexander Tokmakov <tavplubix@clickhouse.com>
Co-authored-by: Alexander Tokmakov <tavplubix@gmail.com>
2023-05-25 12:50:14 +03:00
..
config.d Add zookeeper name in endpoint id (#49780) 2023-05-25 12:50:14 +03:00
top_level_domains
users.d Add CI run with new analyzer enabled 2023-04-12 15:18:28 +00:00
client_config.xml Update tests/config/client_config.xml 2022-08-12 22:01:45 +03:00
decimals_dictionary.xml
dhparam.pem
executable_dictionary.xml
executable_pool_dictionary.xml
ext-en.txt Rewrite NLP tests from integration to functional 2022-08-26 22:36:34 +02:00
ext-ru.txt Rewrite NLP tests from integration to functional 2022-08-26 22:36:34 +02:00
install.sh Add CI run with new analyzer enabled 2023-04-12 15:18:28 +00:00
ints_dictionary.xml
lem-en.bin Add missing file 2022-08-26 23:42:36 +02:00
lsan_suppressions.txt
README.md
regions_hierarchy.txt Add missing tests for legacy geobase 2022-08-26 22:17:49 +02:00
regions_names_en.txt Add missing tests for legacy geobase 2022-08-26 22:17:49 +02:00
server.crt
server.key
strings_dictionary.xml
test_function.xml Disable parameters for non direct executable user defined functions 2022-06-16 16:29:04 +02:00

README.md

ClickHouse configs for test environment

How to use

CI use these configs in all checks installing them with install.sh script. If you want to run all tests from tests/queries/0_stateless and test/queries/1_stateful on your local machine you have to set up configs from this directory for your clickhouse-server. The most simple way is to install them using install.sh script. Other option is just copy files into your clickhouse config directory.

How to add new config

Just place file .xml with new config into appropriate directory and add ln command into install.sh script. After that CI will use this config in all tests runs.