There are 2 different approaches to deal with indexes in Manticore:

Real-time mode requires no index definition in the configuration file, but presence of data_dir directive in searchd section is mandatory. Index files are stored inside the data_dir.

Replication is available only in this mode.

In this mode you can use SQL commands like CREATE TABLE, ALTER TABLE and DROP TABLE to create and change index schema and drop it. This mode is especially useful for real-time and percolate indexes.

Index names are case insensitive in RT mode.

In this mode you can specify index schema in config which will be read on Manticore start and if the index doesn't exist yet it will be created. This mode is especially useful for plain indexes that are built upon indexing data from an external storage.

Dropping indexes is only possible by removing them from the configuration file or by removing the path setting and sending a HUP signal to the server or restarting it.

Index names are case sensitive in this mode.

All index types are supported in this mode.

CREATE TABLE products(title text, price float) morphology='stem_en';

POST /sql -d "mode=raw&query=CREATE TABLE products(title text, price float)  morphology='stem_en'"

$index = new \Manticoresearch\Index($client);
$index->setName('products');
$index->create([
    'title'=>['type'=>'text'],
    'price'=>['type'=>'float'],
]);

utilsApi.sql('mode=raw&query=CREATE TABLE forum(title text, price float)')

res = await utilsApi.sql('mode=raw&query=CREATE TABLE forum(title text, price float)');

utilsApi.sql("mode=raw&query=CREATE TABLE forum(title text, price float)");

index products {
  type = rt
  path = idx
  rt_field = title
  rt_attr_uint = price
  stored_fields = title
}

Query OK, 0 rows affected (0.00 sec)

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

• Add documents
• Update attributes and full-text fields
• Delete documents
• Truncate index
• Change schema online with help of command ALTER
• Define index in a configuration file
• Use UUID for automatic ID provisioning

• Index data with help of indexer
• Link it with sources for easy indexing from external storages
• Update it's killlist_target, it's just not needed as the real-time index takes controls of it automatically