Reopening "Case sensitivity (of facet fields, maybe others?) #504" #1851
Comments
|
It's a bit more nuanced now. Long story short, we have two facet indices which is used to optimize performance for different use cases. In one approach, we have to store the value as they are because they are displayed directly, without touching the disk. The behavior you are seeing now (which seems like a regression) uses this approach because the engine deemed this to be the fastest way to do facets for this query. The older index approach normalizes the facet values but loads them from disk. If you want to use the older index (which can be slower for certain use cases), then use the latest 0.27 RC build and set the following search parameter: |
|
It must be |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Issue is exactly as described earlier. I thought this issue was fixed - but its still occurring. Am I missing something?
?q=*&per_page=0&facet_by=tags&max_facet_values=100gives:filter_by: tags:COVID19MANIPURAnother example
Metadata
Typesense Version:
v26.0
OS:
Ubuntu 22.04.4 LTS
The text was updated successfully, but these errors were encountered: