Creating a table > Creating a distributed table > Creating a local distributed table

Manticore supports distributed tables. They look like usual plain or real-time tables, but internally they are just a 'proxy', or named collection of another child tables used for actual searching. When a query is directed at such table, it is distributed among all tables in the collection. Server collects responses of the queries and processes them as necessary:

applies sorting
recalculates final values of aggregates, etc

From the client's standpoint it looks transparent, as if you just queried any single table.

Distributed tables can be composed from any other tables fitting your requirements

local storage tables (plain table, Real-Time)
remote tables
combined local storage and remote tables
percolate tables (local, remote and combinations)
single local and several remotes or any other combinations

Nesting distributed tables is supported by declaring them with agent (even if they are on the same machine). Distributed tables cannot be declared with local and they will be ignored.

Percolate and template tables should not be mixed with plain and/or RT tables.

Distributed table is defined by type 'distributed' in the configuration file or via SQL clause CREATE TABLE

table foo {
    type = distributed
    local = bar
    local = bar1, bar2
    agent = 127.0.0.1:9312:baz
    agent = host1|host2:tbl
    agent = host1:9301:tbl1|host2:tbl2 [ha_strategy=random retry_count=10]
    ...
}

CREATE TABLE distributed_index type='distributed' local='local_index' agent='127.0.0.1:9312:remote_index'

Either way the key component of a distributed table is a list of children (the tables it points to).

Lines, starting with local = enumerate local tables, served in the same server. Several local tables may be written as several local = lines, or combined into one list, separated by commas.
Lines, starting with agent = enumerate remote tables, served anywhere. Each line represents one agent, or endpoint.

Each agent can include several external locations and options specifying how to work with them.

Note that for remotes the server knows nothing about the type of the table, and it may cause errors, if, say, you issue CALL PQ to remote 'foo' which is not a percolate table.

Creating a local distributed table

A distributed table in Manticore Search doesn't hold any data. Instead it acts as a 'master node' to proxy the demanded query to other tables and provide merged results from the responses it receives from the 'node' tables. A distributed table can connect to local tables or tables located on other servers. The simplest example of a distributed table looks so:

‹›

Configuration file
RT mode
PHP
Python
javascript
Java

📋

table index_dist {
  type  = distributed
  local = index1
  local = index2
  ...
 }

CREATE TABLE local_dist type='distributed' local='index1' local='index2';

$params = [
    'body' => [
        'settings' => [
            'type' => 'distributed',
            'local' => [
                'index1',
                'index2'
            ]
        ]
    ],
    'index' => 'products'
];
$index = new \Manticoresearch\Index($client);
$index->create($params);

utilsApi.sql('CREATE TABLE local_dist type=\'distributed\' local=\'index1\' local=\'index2\'')

res = await utilsApi.sql('CREATE TABLE local_dist type=\'distributed\' local=\'index1\' local=\'index2\'');

utilsApi.sql("CREATE TABLE local_dist type='distributed' local='index1' local='index2'");

Creating a distributed table Remote tables

Creating a distributed table

In a configuration file

Via SQL

Children

Creating a local distributed table