Vector Search not update facet count

[paulchai]

Description

When using the vector search functionality provided by the Typesense InstantSearch Adapter, I noticed that the facet count does not update based on the vector search result. The facet count remains unchanged even when the search query returns a subset of documents that should affect the facet count.

Typesense Version:

• Typesense Version: 0.25.0.rc34
• Typesense InstantSearch Adapter Version: 2.7.0
• instantsearch.js: 4.53.0

[jasonbosco]

Could you try cloning this demo repo and see if you can replicate the issue: https://github.com/typesense/typesense-instantsearch-semantic-search-demo

[paulchai]

Ok let me rewrite the issue:

Description

I am using the vector search feature provided by Typesense InstantSearch Adapter, and I have noticed an inconsistency with the facet count display. When I perform a vector search and it returns a subset of documents, the facet count should logically update to reflect this new data set. However, it remains unchanged.

Steps to Reproduce

To reproduce this issue, follow these steps:

1. Clone the repo: https://github.com/typesense/typesense-instantsearch-semantic-search-demo
2. Run the project and type a few search words in the search text field. For instance, 'light weight case'.

Expected Behaviour

I would expect the count on the refinement list (on the left side) to update based on the vector search result, similar to the behaviour on https://ecommerce-store.typesense.org/. For example, when searching for "light weight case", the facet count for "Cell Phone Accessories" should update to reflect the number of matching results, say 1,983, instead of remaining at its original count.

Actual Behaviour

Contrary to the above expectation, the facet count remains unchanged, regardless of the search result. For example, "Cell Phone Accessories" stays at 2,836.

Metadata

• Typesense Server Version: 0.25.0.rc34
• Typesense InstantSearch Adapter Version: 2.7.0
• Instantsearch.js Version: 4.53.0

[sif-gondy]

Any updates on this? I have the same problem.