Facet Values Treated as Same Due to Dash Ignored
TLDR Aljosa encountered an issue where different facet values were considered identical due to a dash. Jason explained that special characters are indexed in newer versions. Aljosa resolved to enable this option.
Nov 27, 2021 (22 months ago)
I have two distinct facet values for a certain field.
Example values (not exact ones I have)
When displayed (through the instant search adapter in a facet), they show up separately. But when selecting either of these values, they get treated as the same value so the total results returned is equivalent both combined (and selecting both doesn't change anything since all results are already returned).
I imagine it's just the dash that gets ignored so both get turned into "thisword" or something, but it seems like strange default behavior and doesn't appear documented.
Nov 28, 2021 (22 months ago)
Indexed 2764 threads (79% resolved)
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.
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.
Facet Count Discrepancy in Integration Testing with Typesense
SamHendley faced an issue with inconsistent facet counts and found it was due to mixed case input and punctuation. Kishore Nallan confirmed that Typesense normalizes values before indexing, affecting the facet count. They then discussed addition of preconditioning data to match Typesense.