Mobile Autocomplete Issue in Web Development
TLDR Prime is experiencing a problem with the autocomplete feature on mobile view. He reached out to both Kishore Nallan and Jason for assistance. Multiple solutions were suggested such as refraining from triggering requests to Typesense for empty queries, but the issue persists.
1
Oct 05, 2023 (1 month ago)
Prime
07:15 AMPrime
03:15 PMKishore Nallan
03:20 PMPrime
03:33 PMPrime
06:56 PMOct 06, 2023 (1 month ago)
Jason
12:12 AMJason
12:13 AMOct 10, 2023 (1 month ago)
Prime
06:34 AM1
Prime
06:34 AMPrime
06:35 AMOct 11, 2023 (1 month ago)
Jason
02:38 PMPrime
06:09 PMPrime
06:10 PMOct 12, 2023 (1 month ago)
Prime
05:23 AMPrime
05:23 AMJason
04:50 PMcurl '' -H 'X-TYPESENSE-API-KEY: <API_KEY>'
Essentially empty values for q, and facetquery... Along with a group_by. This group_by is what's slowing down this query to almost 3.5s, and the loading icon shows up during this time.
A couple of solutions to try:
1. Do you intend to show _all results when the search bar is clicked? If so, you want to consider adding
use_cache=true
as a query parameter. 2. If you don't intend to show all results with no terms entered in the autocomplete, you could check for an empty query in the code and not trigger the request to Typesense if that's the case.
Prime
06:13 PMPrime
06:14 PMJason
06:18 PMMay I know how many CPU cores you have on the server that's running Typesense?
Jason
06:18 PMThis might be the solution
Prime
06:21 PMJason
06:21 PMPrime
06:25 PMPrime
06:26 PMJason
06:27 PMGET /debug
will return the versionPrime
06:32 PMJason
06:39 PMq
and query_by: categories
?Prime
06:50 PMPrime
06:50 PMJason
06:51 PMJason
06:52 PMJason
06:53 PMPrime
06:57 PMTypesense
Indexed 3005 threads (79% resolved)
Similar Threads
Dealing with Timeout Issues with Typesense in Algolia Plugin
Prime encounters timeout while making a typesense request inside a custom algolia autocomplete plugin. Though recommended solutions were tried, the issue wasn't fully resolved.
Troubleshooting Typesense Data Load Issues on Ecommerce Platform
Dương requested help with Typesense data load issues on non-localhost systems. Kishore Nallan and David helped him isolate the problem. It was finally resolved when Dương identified and corrected a router configuration issue.
Issue Resolution and Upgrade Problems in Typesense Version 0.26rc16
Ankit reported an issue with Typesense, which was addressed by Kishore Nallan and Jason. However, Ankit experienced difficulties while trying to upgrade, with the server status showing as "Not ready or lagging" 503. The resolution remains incomplete.
Transitioning from Meilisearch to Typesense - Questions and Suggestions
Al is moving from Meilisearch to Typesense and asked for similar matching information features. They also proposed adding daily backups. Kishore Nallan helped them find a workaround, while noting expected complexities, and agreed to include their suggestions in their backlog.
Resolving Issues While Upgrading Typesense Server
Ayush had queries about upgrading their Typesense server and updating collections using auto-embeddings. Kishore Nallan clarified all issues, but later discovered that reindexing of non auto-embedded vector fields only is currently supported during altering.