Stas
Stas
we have only instruction on ManticoreSearch installation at the [manual](https://manual.manticoresearch.com/Installation/Installation) but not about package upgrade. The only mention [Changelog#Upgrade](https://manual.manticoresearch.com/Changelog#Upgrade) is > In case you run Manticoresearch in a distributed environment...
daemon with the version `6.2.13 a28f6e087@231219 dev (columnar 2.2.5 c323cec@231127) (secondary 2.2.5 c323cec@231127)` after create table, populate table and flush data into disk chunk [q.txt](https://github.com/manticoresoftware/manticoresearch/files/13730163/q.txt) the following query ``` select...
after [REGEX](https://github.com/manticoresoftware/manticoresearch/issues/1541) full-text was implemented in master branch there are still issues left: - EXPLAIN does not take into account REGEX full text operator - CALL KEYWORDS does not take...
there is a SphinxQL statement for node to join the cluster [JOIN CLUSTER](https://manual.manticoresearch.com/Creating_a_cluster/Setting_up_replication/Joining_a_replication_cluster#Joining-a-replication-cluster) but for node to leave the cluster the is no direct command. For now it could be...
### Bug Description: When `listen = 127.0.0.1:9312` used on Windows buddy that starts in the docker can not communicate with daemon and daemon replies with error ``` mysql -h 127.0.0.1...
if one node in the cluster was shut for a period of time and cluster adds index then the old node that joins the cluster back and receives IST fails...
indexing attributes into secondary index opens temporary files for every attribute to collect raw values. It could be better to index raw values into the different bins of the one...
show plan output is valid for plain index or RT index without RAM segments but with the single disk chunk. But for RT index with multiple disk chunks every disk...
Galera use IST on node restart only node seqno saved well on node shutdown overwise Galera issue SST for node to join the cluster. That is why if node got...
adding multiple table into cluster and join the new nodes into cluster causes the race - `ALTER cluster name ADD table_nameX` - the `tableX` is send into cluster nodes via...