Emptying a table

The table can be emptied with a TRUNCATE TABLE SQL statement or with a truncate() PHP client function.

Here is the syntax for the SQL statement:

TRUNCATE TABLE index_name [WITH RECONFIGURE]

When this statement is executed, it clears the RT table completely. It disposes the in-memory data, unlinks all the table data files, and releases the associated binary logs.

A table can also be emptied with DELETE FROM index WHERE id>0, but it’s not recommended as it’s much slower than TRUNCATE.

• SQL
• JSON
• PHP
• Python
• javascript
• Java

SQL JSON PHP Python javascript Java

TRUNCATE TABLE products;

POST /cli -d "TRUNCATE TABLE products"

$params = [ 'index' => 'products' ];
$response = $client->indices()->truncate($params);

utilsApi.sql('TRUNCATE TABLE products')

res = await utilsApi.sql('TRUNCATE TABLE products');

utilsApi.sql("TRUNCATE TABLE products");

Response

Query OK, 0 rows affected (0.02 sec)

{
"total":0,
"error":"",
"warning":""
}

Array(
    [total] => 0
    [error] => 
    [warning] => 
)

{u'error': u'', u'total': 0, u'warning': u''}

{"total":0,"error":"","warning":""}

{total=0, error=, warning=}

One of the possible uses of this command is before attaching a table.

When RECONFIGURE option is used new tokenization, morphology, and other text processing settings specified in the config take effect after the table gets cleared. In case the schema declaration in config is different from the table schema the new schema from config got applied after table get cleared.

With this option clearing and reconfiguring a table becomes one atomic operation.

• SQL
• HTTP
• PHP
• Python
• javascript
• Java

SQL HTTP PHP Python javascript Java

TRUNCATE TABLE products with reconfigure;

POST /cli -d "TRUNCATE TABLE products with reconfigure"

$params = [ 'index' => 'products', 'with' => 'reconfigure' ];
$response = $client->indices()->truncate($params);

utilsApi.sql('TRUNCATE TABLE products WITH RECONFIGURE')

res = await utilsApi.sql('TRUNCATE TABLE products WITH RECONFIGURE');

utilsApi.sql("TRUNCATE TABLE products WITH RECONFIGURE");

Response

Query OK, 0 rows affected (0.02 sec)

{
"total":0,
"error":"",
"warning":""
}

Array(
    [total] => 0
    [error] => 
    [warning] => 
)

{u'error': u'', u'total': 0, u'warning': u''}

{"total":0,"error":"","warning":""}

{total=0, error=, warning=}

Manticore cluster

Manticore Search is a highly distributed system and consists of all the needed components to allow you build a highly available and scalable setup of a database for search:

• distributed table allowing sharding
  • Mirroring for high availability
  • Load balancing for high scalability
• Replication for data safety

Manticore Search is extremely flexible in terms of how you setup your cluster, there’s no limitations and it’s up to you how you design it. Just learn the tools mentioned above and use them to achieve your goal.

Adding a new node

To add another node to a cluster just start another node of Manticore and make sure it’s accessible by other nodes in your cluster. Then use a distributed table to connect one node with another and replication for data safety.