#community-help

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.

22mo

Join the chat

Nov 27, 2021 (22 months ago)

Photo of md5-6bb7313b20c5179141d6908d6c09b2d5

Aljosa

09:19 PM

Having trouble determining whether a certain behaviour is expected or known.

I have two distinct facet values for a certain field.

Example values (not exact ones I have)

• This-Word
• Thi-Sword
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.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

10:04 PM

This was the default behavior in v0.21… If you use the latest RC version we’ve added some special characters to be indexed by default

10:05

Jason

10:05 PM

More context here: https://typesense-community.slack.com/archives/C01P749MET0/p1637962507427600

Nov 28, 2021 (22 months ago)

Aljosa

03:45 AM

Awesome! I'm on RC34 of 0.22 so I'll enable that option 🙂

03:45

Aljosa

03:45 AM

tyvm !

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

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

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.

22mo

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.

11mo