Configuring InstantSearch.js Parameters and Comparing Search Results
TLDR John is having difficulty configuring InstantSearch.js parameters. Jason suggested how to utilize facet_by
and filter_by
widgets and advised checking network for search parameters. They also asked John to open an issue on the unexpected need for manual _text_match
addition.
2
Jun 01, 2021 (30 months ago)
John
04:40 PMJohn
04:44 PMadditionalSearchParameters: {
queryBy: 'categories,artname,artistname,color1,color2,tags,dimensions',
sortBy: 'numsales:desc'
},
Jason
05:03 PMquery_by
and include_fields
can be directly configured via additionalSearchParameters
in Instantsearch. This is because Instantsearch manages the other parameters internally through their widgets.So to use
facet_by
and filter_by
you want to use one of the refinement (or filter) widgets that Instantsearch offers. For sort_by, there's the sort widget - [here's](https://github.com/typesense/typesense-instantsearch-adapter/issues/9#issuecomment-710091167) how you configure it for Typesense. If you want to configure default params, have a look at the configure widget.1
John
05:27 PM_text_match:desc
sortBy parameter? Is it an implicit one or do I need to put it in there as well?
Jason
05:29 PMJohn
05:29 PMJohn
11:23 PMqueryBy
and sortBy
lines, right? Because at some point I had thought the Include Fields
also were modifying the output...John
11:25 PMJohn
11:26 PMJason
11:27 PMJohn
11:32 PMJohn
11:38 PMOn my website:
"sort_by": "numsales:desc",
On the cloud:
"sort_by": "numsales:desc,_text_match:desc",
John
11:38 PM_text_match
manually?Jason
11:40 PM_text_match
should get added to the end automatically...Jason
11:40 PMJohn
11:41 PMJason
11:42 PM1
Jun 03, 2021 (30 months ago)
Jason
02:25 AM"sort_by": "numsales:desc"
and "sort_by": "numsales:desc,_text_match:desc"
produced different results? Wasn't replicate it, so I'm wondering if there's something else that might be going onTypesense
Indexed 2786 threads (79% resolved)
Similar Threads
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.
Resolve Facets and Sorting Issues with Typesense
Ethan needed assistance with getting all facet values and sorting results by date using Typesense. Jason provided guidance on how to use Typesense properties to accomplish these tasks, and resolved issues related to specific use-cases provided by Ethan and Rushil.
Fixing Multiple Document Retrieval in Typesense
Phil needed an efficient way to retrieve multiple documents by id. Kishore Nallan proposed a solution available in a pre-release build. After some bug fixing regarding id matching by Jason and Kishore Nallan, Phil successfully tested the solution.
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.
Resolving Issues with 'React-InstantSearch'
robert was having trouble merging results from different collections using `react-instantsearch` and was facing issues with undefined highlight results. After much discussion, Jason provided a solution using `collectionSpecificSearchParameters` and `highlight_full_fields` to solve the problem.