#community-help

Typesense Facet Query Issue and Resolution

TLDR Stefan wanted to have typesense return count: 0 for filtered out facets, which was not supported. They shared a workaround using a server data call. The solution involved adding "facets: [this.filterConfig.attribute]," for the server adapter to work. Kishore Nallan acknowledged the resolution.

27mo

Join the chat

Aug 13, 2021 (27 months ago)

Photo of md5-d6c265b4792dbf0a1d6ae378f39d8736

Stefan

01:20 PM

Is there a way to make typesense return count: 0 for facet that are filtered out?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

02:13 PM

👋 You mean if you apply a filter like brand: foo then the facet count should have foo: 0 as a value?

Stefan

02:21 PM

yes

02:21

Stefan

02:21 PM

but I think it's not possible and not intended

02:22

Stefan

02:22 PM

algolia provides this working around: https://www.algolia.com/doc/guides/building-search-ui/widgets/customize-an-existing-widget/vue/#display-facets-with-no-matches

But I can't seem to get it working

02:22

Stefan

02:22 PM

If I do what they suggest I get this error when calling the server for initial data

FacetSearchResponseAdapter.js?7637:32 Uncaught (in promise) TypeError: Cannot read property 'counts' of undefined
    at FacetSearchResponseAdapter._adaptFacetHits (FacetSearchResponseAdapter.js?7637:32)
    at FacetSearchResponseAdapter.adapt (FacetSearchResponseAdapter.js?7637:45)
    at eval (TypesenseInstantsearchAdapter.js?7ea0:114)
    at Array.map (<anonymous>)
    at TypesenseInstantsearchAdapter._callee2$ (TypesenseInstantsearchAdapter.js?7ea0:110)
    at tryCatch (runtime.js?96cf:63)
    at Generator.invoke [as _invoke] (runtime.js?96cf:293)
    at Generator.eval [as next] (runtime.js?96cf:118)
    at asyncGeneratorStep (asyncToGenerator.js?c973:3)
    at _next (asyncToGenerator.js?c973:25)

02:30

Stefan

02:30 PM

okay got it working, we have to add "facets: [this.filterConfig.attribute]," in order for the adapter to work

Kishore Nallan

02:32 PM

👍

Typesense

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

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Typesense Products Filtering Issue with Mixed AND+OR Filtering

Dmytro faced issues in implementing mixed AND+OR filtering for product filtering on Typesense using `'typesense-instantsearch-adapter'` despite using several approaches and facets. Jason suggested increasing the number of facets fetched and trying a different server version but the issue remains.

16mo

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

Range Filtering and Faceting Discussion

Phil asked about the requirements for range filtering, which Jason explained does not always require faceting. Discussion about different possibilities with Algolia and Typesense ensued, resulting in Phil successfully utilizing the 'Configure' widget.

25mo

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

Production Typesense Issue with Unexpected Filter Behavior

Ankit flagged a problem with a specific filter on the production server of Typesense. After several exchanges regarding optimisation and version checks, Kishore Nallan provided latest builds to troubleshoot. The filtering within facets issue persists and potential edge cases are being investigated.

1mo