The index 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 index completely. It disposes the in-memory data, unlinks all the index data files, and releases the associated binary logs.
An index can also be emptied with DELETE FROM index WHERE id>0
, but it's not recommended as it's much slower than TRUNCATE
.
- SQL
- HTTP
- PHP
- Python
- javascript
- Java
TRUNCATE TABLE products;
Query OK, 0 rows affected (0.02 sec)
One of the possible uses of this command is before attaching an index.
When RECONFIGURE
option is used new tokenization, morphology, and other text processing settings specified in the config take effect after the index gets cleared. In case the schema declaration in config is different from the index schema the new schema from config got applied after index get cleared.
With this option clearing and reconfiguring an index becomes one atomic operation.
- SQL
- HTTP
- PHP
- Python
- javascript
- Java
TRUNCATE TABLE products with reconfigure;
Query OK, 0 rows affected (0.02 sec)
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 index 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.
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 index to connect one node with another and replication for data safety.