#community-help

Understanding Indexing and Cloning in Typesense

TLDR Calum learned about immediate indexing in Typesense and the new feature of index cloning from Jason.

Powered by Struct AI

1

Oct 14, 2022 (14 months ago)
Calum
Photo of md5-162162ca008ade58341a6453c698d386
Calum
10:36 PM
Hey guys! I’m new to typesense. I have a quick question - if I index some data, does the indexing happen straight away as in it is searchable immediately once I get a 200 response? Or is it like elasticsearch where it indexes a few seconds later?
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
10:38 PM
Indexing is synchronous in Typesense, so if the API returns a 200, it means the data has been indexed and will be available for search.

That said, when running in HA clustered mode, each node is eventually consistent, so there will be a few seconds delay from a 200 and when the data shows up in search on each node, depending on the network latency between the nodes

1

Calum
Photo of md5-162162ca008ade58341a6453c698d386
Calum
11:01 PM
Thanks for this Jason
11:02
Calum
11:02 PM
Got another follow on question, you clone/duplicate an index?
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
11:07 PM
Meaning in clustered mode, or are you asking if you can clone a collection in general?
Oct 15, 2022 (14 months ago)
Calum
Photo of md5-162162ca008ade58341a6453c698d386
Calum
01:09 PM
Clone in general
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
01:10 PM
We’ve added support for cloning a collection in the recent rc build 0.24.0.rcn17: https://gist.github.com/jasonbosco/8e16adeac8ff35ece4359fc9f0527511
Calum
Photo of md5-162162ca008ade58341a6453c698d386
Calum
01:10 PM
That’s awesome!

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Troubleshooting Typesense Document Import Error

Christopher had trouble importing 2.1M documents into Typesense due to memory errors. Jason clarified the system requirements, explaining the correlation between RAM and dataset size, and ways to tackle the issue. They both also discussed database-like query options.

3

30
11mo

Improving Typesense Query Performance

Jonathan queried about slower than expected typesense query performance. Jason and Kishore Nallan offered solutions and explanations. After a series of tests, Jonathan found other queries returned results quickly, indicating the issue was specific to the original query.

3

26
13mo

Optimizing Typesense Implementation for Large Collections

Oskar faced performance issues with his document collection in Typesense due to filter additions. Jason suggested trying a newer Typesense build and potentially partitioning the data into country-wise collections. They also discussed reducing network latency with CDN solutions.

5

67
11mo

Revisiting Typesense for Efficient DB Indexing and Querying

kopach experienced slow indexing and crashes with Typesense. The community suggested to use batch import and check the server's resources. Improvements were made but additional support was needed for special characters and multi-search queries.

1

46
9mo

Addressing Typesense Server Issues and Optimization Needs

Robert had an issue with a 'stuck' typesense server. Jason and Kishore Nallan gave advice on handling writes, configuration for high search volumes, and running multiple typesense instances. They also recommended monitoring CPU usage and updating the server version for bug fixes.

1

30
14mo