#community-help

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.

30mo

Join the chat

Jun 01, 2021 (30 months ago)

Photo of md5-7a0ab48aa8979a59e1d8c3919797c1f8

John

04:40 PM

Hi, I am having a hard time configuring the my InstantSearch.js to reproduce this. Anyone could help me?

04:44

John

04:44 PM

Right now this is what I have:

additionalSearchParameters: {
    queryBy: 'categories,artname,artistname,color1,color2,tags,dimensions',
    sortBy: 'numsales:desc'
  },

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

05:03 PM

John Out of the parameters in the screenshot only query_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.

John

05:27 PM

OK, thanks, and what about the

_text_match:desc

sortBy parameter? Is it an implicit one or do I need to put it in there as well?

Jason

05:29 PM

It's implicitly added as the first sort_by parameter by Typesense

John

05:29 PM

OK, that's what I thought

11:23

John

11:23 PM

OK, here, I have another question Jason: what determines the results set is only, in fact, the queryBy and sortBy lines, right? Because at some point I had thought the Include Fields also were modifying the output...

11:25

John

11:25 PM

Now, what I am not understanding though is why I have different results on my website compared to the admin interface of https://cloud.typesense.org/

11:26

John

11:26 PM

On the Cloud, the results are much better, and I don't know why...

Jason

11:27 PM

It's most likely that all search parameters are not being included... If you look at the network tab in both the cloud console and your website as search requests are made, you'll be able to get the exact search parameters that are being sent to Typesense and see what the differences in parameters are

John

11:32 PM

OK perfect, I will compare!

11:38

John

11:38 PM

Comparison
On my website:
"sort_by": "numsales:desc",
On the cloud:
"sort_by": "numsales:desc,_text_match:desc",

11:38

John

11:38 PM

So it seems I need to add the _text_match manually?

Jason

11:40 PM

Hmmm, _text_match should get added to the end automatically...

11:40

Jason

11:40 PM

Let's try that though

John

11:41 PM

Don't know why but it wasn't. I added it manually and it now works!

Jason

11:42 PM

Glad it works when you added it by hand! But this is different from expected behavior - it should automatically add _text_match at the end if it's not specified. Will take a look shortly

Jun 03, 2021 (30 months ago)

Jason

02:25 AM

John Mind opening a github issue in the typesense repo with a minimal sample dataset reproducing the issue you saw, where "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 on

Typesense

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

Indexed 2786 threads (79% resolved)

Join Our Community Manage subscription

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.

111

6mo

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.

2mo

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.

24mo

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.

19mo

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.

15mo