mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-11-28 02:21:59 +00:00
67c2e50331
* update presentations * CLICKHOUSE-2936: redirect from clickhouse.yandex.ru and clickhouse.yandex.com * update submodule * lost files * CLICKHOUSE-2981: prefer sphinx docs over original reference * CLICKHOUSE-2981: docs styles more similar to main website + add flags to switch language links * update presentations * Less confusing directory structure (docs -> doc/reference/) * Minify sphinx docs too * Website release script: fail fast + pass docker hash on deploy * Do not underline links in docs * shorter * cleanup docker images * tune nginx config * CLICKHOUSE-3043: get rid of habrastorage links * Lost translation * CLICKHOUSE-2936: temporary client-side redirect * behaves weird in test * put redirect back * CLICKHOUSE-3047: copy docs txts to public too * move to proper file * remove old pages to avoid confusion * Remove reference redirect warning for now * Refresh README.md * Yellow buttons in docs * Use svg flags instead of unicode ones in docs * fix test website instance * Put flags to separate files * wrong flag * Copy Yandex.Metrica introduction from main page to docs * Yet another home page structure change, couple new blocks (CLICKHOUSE-3045) * Update Contacts section * CLICKHOUSE-2849: more detailed legal information * CLICKHOUSE-2978 preparation - split by files * More changes in Contacts block * Tune texts on index page * update presentations * One more benchmark * Add usage sections to index page, adapted from slides * Get the roadmap started, based on slides from last ClickHouse Meetup * CLICKHOUSE-2977: some rendering tuning * Get rid of excessive section in the end of getting started * Make headers linkable * CLICKHOUSE-2981: links to editing reference - https://github.com/yandex/ClickHouse/issues/849 * CLICKHOUSE-2981: fix mobile styles in docs * Ban crawling of duplicating docs * Open some external links in new tab * Ban old docs too * Lots of trivial fixes in english docs * Lots of trivial fixes in russian docs * Remove getting started copies in markdown * Add Yandex.Webmaster * Fix some sphinx warnings * More warnings fixed in english docs * More sphinx warnings fixed * Add code-block:: text * More code-block:: text * These headers look not that well * Better switch between documentation languages * merge use_case.rst into ya_metrika_task.rst * Edit the agg_functions.rst texts * Add lost empty lines * Lost blank lines * Add new logo sizes * update presentations * Next step in migrating to new documentation * Fix all warnings in en reference * Fix all warnings in ru reference * Re-arrange existing reference * Move operation tips to main reference * Fix typos noticed by milovidov@ * Get rid of zookeeper.md * Looks like duplicate of tutorial.html * Fix some mess with html tags in tutorial * No idea why nobody noticed this before, but it was completely not clear whet to get the data * Match code block styling between main and tutorial pages (in favor of the latter) * Get rid of some copypaste in tutorial * Normalize header styles * Move example_datasets to sphinx * Move presentations submodule to website * Move and update README.md * No point in duplicating articles from habrahabr here * Move development-related docs as is for now * doc/reference/ -> docs/ (to match the URL on website) * Adapt links to match the previous commit * Adapt development docs to rst (still lacks translation and strikethrough support) * clean on release * blacklist presentations in gulp * strikethrough support in sphinx * just copy development folder for now * fix weird introduction in style article * Style guide translation (WIP) * Finish style guide translation to English * gulp clean separately * Update year in LICENSE * Initial CONTRIBUTING.md * Fix remaining links to old docs in tutorial * Some tutorial fixes * Typo * Another typo * Update list of authors from yandex-team accoding to git log
74 lines
3.1 KiB
ReStructuredText
74 lines
3.1 KiB
ReStructuredText
remote
|
|
------
|
|
|
|
``remote('addresses_expr', db, table[, 'user'[, 'password']])``
|
|
|
|
or
|
|
|
|
``remote('addresses_expr', db.table[, 'user'[, 'password']])``
|
|
|
|
- Allows accessing a remote server without creating a Distributed table.
|
|
|
|
``addresses_expr`` - An expression that generates addresses of remote servers.
|
|
|
|
This may be just one server address. The server address is host:port, or just the host. The host can be specified as the server name, or as the IPv4 or IPv6 address. An IPv6 address is specified in square brackets. The port is the TCP port on the remote server. If the port is omitted, it uses tcp_port from the server's config file (by default, 9000).
|
|
|
|
Note: As an exception, when specifying an IPv6 address, the port is required.
|
|
|
|
Examples:
|
|
|
|
.. code-block:: text
|
|
|
|
example01-01-1
|
|
example01-01-1:9000
|
|
localhost
|
|
127.0.0.1
|
|
[::]:9000
|
|
[2a02:6b8:0:1111::11]:9000
|
|
|
|
Multiple addresses can be comma-separated. In this case, the query goes to all the specified addresses (like to shards with different data) and uses distributed processing.
|
|
|
|
Example:
|
|
|
|
.. code-block:: text
|
|
|
|
example01-01-1,example01-02-1
|
|
|
|
Part of the expression can be specified in curly brackets. The previous example can be written as follows:
|
|
|
|
.. code-block:: text
|
|
|
|
example01-0{1,2}-1
|
|
|
|
Curly brackets can contain a range of numbers separated by two dots (non-negative integers). In this case, the range is expanded to a set of values that generate shard addresses. If the first number starts with zero, the values are formed with the same zero alignment.
|
|
The previous example can be written as follows:
|
|
|
|
.. code-block:: text
|
|
|
|
example01-{01..02}-1
|
|
|
|
If you have multiple pairs of curly brackets, it generates the direct product of the corresponding sets.
|
|
|
|
Addresses and fragments in curly brackets can be separated by the pipe (|) symbol. In this case, the corresponding sets of addresses are interpreted as replicas, and the query will be sent to the first healthy replica. The replicas are evaluated in the order currently set in the 'load_balancing' setting.
|
|
|
|
Example:
|
|
|
|
.. code-block:: text
|
|
|
|
example01-{01..02}-{1|2}
|
|
|
|
This example specifies two shards that each have two replicas.
|
|
|
|
The number of addresses generated is limited by a constant. Right now this is 1000 addresses.
|
|
|
|
Using the 'remote' table function is less optimal than creating a Distributed table, because in this case, the server connection is re-established for every request. In addition, if host names are set, the names are resolved, and errors are not counted when working with various replicas. When processing a large number of queries, always create the Distributed table ahead of time, and don't use the 'remote' table function.
|
|
|
|
The 'remote' table function can be useful in the following cases:
|
|
* Accessing a specific server for data comparison, debugging, and testing.
|
|
* Queries between various ClickHouse clusters for research purposes.
|
|
* Infrequent distributed requests that are made manually.
|
|
* Distributed requests where the set of servers is re-defined each time.
|
|
|
|
The username can be omitted. In this case, the 'default' username is used.
|
|
The password can be omitted. In this case, an empty password is used.
|