Improved Sorting Options for Relevant Facets
TLDR Stefan proposes a feature for sorting facets based on other fields not just hit counts. Kishore Nallan agrees and emphasizes the need for the facet value to remain constant across different documents.
Nov 24, 2022 (13 months ago)
Kishore Nallan11:39 AM
Imagine thousands of products where each product has 20 ingredients or so.
Almost all of them contain water, but that is pretty irrelevant.
I would like to show the ingredients in the default view that "make the difference" in a product.
Right now the only way I see on how to get those results is by creating a separate field in the schema that only contains the "relevant" ingredients.
Kishore Nallan12:26 PM
So this feature would def. fix my issue.
Kishore Nallan12:52 PM
Kishore Nallan01:03 PM
Indexed 3015 threads (79% resolved)
Understanding Facet Results in Typesense
Prabhu had difficulty understanding the count results of his facet results in Typesense. Kishore Nallan explained the behaviour and suggested creating a Github issue for a feature request to modify count behaviour.
Handling Large Amount of Facet Values
Dima asked about handling large amounts of facet values. Jason assured that it is fine and suggested setting `max_facet_values` to a large number.
Setting dynamic range faceting in Typesense
Jacob requested dynamic range faceting in Typesense, and explanation for fetching max/min values. Kishore Nallan clarified pricing bucket sizes were user dependent and explained the stats return as part of facet results.
Resolve Facets and Sorting Issues with Typesense
Ethan needed assistance with getting all facet values and sorting results by date using Typesense. Jason provided guidance on how to use Typesense properties to accomplish these tasks, and resolved issues related to specific use-cases provided by Ethan and Rushil.
Improving System Performance and Typesense Query Efficiency
SamHendley was experiencing performance issues with Typesense's large-scale system testing and proposed several improvements. Both Jason and Kishore Nallan addressed the suggestions and corrected some misconceptions. They provided further clarification and recommended upgrades for better performance.