#community-help

Tolerance for Non-Existent Facets in Typesense

TLDR Dan requested if Typesense could tolerate non-existent facets. Kishore Nallan asked for a GitHub issue creation for the feature and Dan obliged.

14mo

Join the chat

Jul 28, 2022 (14 months ago)

Photo of md5-f8f7b04dda4a09dec991cdc07f4d9c64

Dan

10:15 AM

Could TS tolerate being asked for a facet that doesn’t exist, instead of rejecting the call? The way we’re using programatic facets means that we don’t always have every facet - and it’s annoying have to check if a facet exists before asking for it.

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

10:17 AM

We don't have a way to ignore non-existent facet fields. Can you please create a github issue for that. Happy to consider it as a feature request which we will plan into our roadmap for the future releases.

Dan

10:20 AM

https://github.com/typesense/typesense/issues/681

Typesense

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

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Faceting issue with Products Collections in Typesense

Carl was unable to facet on a string array. Kishore Nallan and Jason advised ensuring facet counts were being returned and offered to assist in troubleshooting. Issue resolved upon Carl realizing no data was saved in the database.

24mo

Typesense Facet Query Issue and Resolution

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.

25mo

Faceting Objects in Typesense

John wants to facet objects in Typesense, but faces issues. Kishore Nallan suggests creating a feature request on GitHub.

6mo