Typesense Capabilities and Troubleshooting Queries
TLDR A had issues with refinement lists and analytics in Typesense. Jason provided a possible solution and recommended the analytics widget. They clarified import size limits and helped identify a filter issue in A's query. Upgrade options are in Typesense's roadmap.
3
1
Mar 26, 2021 (34 months ago)
A
01:39 AMi've been trying for a few days to get multiple refinement lists to show up in the UI, but to no luck. I'm not very good with npm and these @import js workflows, so i just found an entirely compiled full vanilla JS and got it working that way. how can i get multiple refinementlists?
instantsearch.widgets.refinementList({
container: '#refinement-list',
attribute: 'tags',
searchable: true,
searchablePlaceholder: 'Search Tags',
showMore: true,
showMoreLimit: 20,
}),
extra: are search analytics going to be coming to typesense? as in, who searched what and when..
extra2: how many imports can typesense hosted do at one time? I've been doing 1000-2000 imports at a time because higher ones timeout
Jason
01:55 AMsearch.addWidgets()
to get the first refinementList to show up?Jason
01:58 AMinstantsearch.addWidgets([instantsearch.widgets.refinementList({...}), instantsearch.widgets.refinementList({...})])
might work...
1
Jason
01:59 AMWe currently don't have server-side analytics in Typesense. Instead I'd recommend using the analytics widget in InstantSearch.js to hook into search queries and send the data to either a web analytics platform like GA / Amplitude, etc or send it to a backend of their choice. With web analytics tools you usually get additional context around search terms like (search terms with the higher conversion rate), which server-side analytics won't be able to do.
1
Jason
02:01 AMI've tried imports of up to 3GB in one import call with millions of records on a 16GB RAM, 4vCPU machine.
So the answer to your question would depend on the size of the machine you're using.
1
A
02:18 AMA
02:18 AMA
02:21 AMJason
04:34 AMA
04:35 AMA
04:36 AMclient.collections.retrieve
which shows a correct number of documents, but the search interface is a few thousand off
Jason
04:36 AMA
04:37 AM{1=>7, 3=>593, 2=>13913}
1 = not set, 3 = dental, 2 = medical
A
04:37 AMA
04:38 AMA
04:39 AM "name"=>"mcqs",
"num_documents"=>14506,
"num_memory_shards"=>4},
{"created_at"=>1616719676,
@typesense.collections.retrieve
ETHON: Libcurl initialized
ETHON: performed EASY effective_url= response_code=200 return_code=ok total_time=0.589906
=> [{"created_at"=>1616732031,
Jason
04:40 AMA
04:40 AM13913 + 593 + 7 = 14513
A
04:40 AMJason
04:40 AMA
04:42 AMcurl '' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:83.0) Gecko/20100101 Firefox/83.0' -H 'Accept: application/json, text/plain, */*' -H 'Accept-Language: en-US,en;q=0.5' --compressed -H 'Referer: ' -H 'Content-Type: text/plain' -H 'Origin: ' -H 'DNT: 1' -H 'Connection: keep-alive' --data-raw '{"searches":[{"query_by":"id","num_typos":2,"sort_by":"","highlight_full_fields":"id","collection":"mcqs","q":"*","facet_by":"tags,user,multiple_choice_question_classification,published","filter_by":"published:=[true]","max_facet_values":8,"page":1,"facet_query":"tags:h","per_page":0}]}'
A
04:42 AMJason
04:43 AMA
04:43 AMA
04:43 AMA
04:43 AMJason
04:44 AMA
04:44 AMA
04:44 AMA
04:44 AMA
04:45 AMJason
04:46 AM1
Typesense
Indexed 3011 threads (79% resolved)
Similar Threads
Troubleshooting Typesense Setup and Understanding Facets and Keywords
Demitri encountered errors when exploring Typesense for the first time. Jason guided them through troubleshooting and discussed facets, keyword settings, and widget configurations. Helin shared a Python demo app and its source code to help Demitri with their project.
Network Errors and Duplicate Requests in Typesense
Ethan and Rushil were experiencing more than 300 network errors and duplicate requests from Typesense. After rigorous troubleshooting, Jason identified the issue as an Instantsearch-induced multiple re-rendering and implemented a fix. Multiple requests reduced, but networking errors persisted, suggested to be due to client-side internet connectivity.
Resolving Typesense Analytics "top_queries" Collection Issue
Zain faced issues with typesense analytics and an empty "top_queries" collection. Jason and Kishore Nallan assisted in troubleshooting, identified a bug, and suggested a fix in `0.25.0.rc66`. The fix worked for Zain.
Phrase Search Relevancy and Weights Fix
Jan reported an issue with phrase search relevancy using Typesense Instantsearch Adapter. The problem occurred when searching phrases with double quotes. The team identified the issue to be related to weights and implemented a fix, improving the search results.
Solving Typesense Docsearch Scraper Issues
Sandeep was having issues with Typesense's docsearch scraper and getting fewer results than with Algolia's scraper. Jason helped by sharing the query they use and advised checking the running version of the scraper. The issue was resolved when Sandeep ran the non-base regular docker image.