Precision Issues with Int64 Numeric Field in Go Client
TLDR SamHendley expressed concerns about precision and rounding problems with an int64 numeric field using a timestamp. The problem was traced back to a conversion issue in the go client, prompting SamHendley to suggest updating the openapi spec to use double for reduced errors.
Nov 03, 2022 (11 months ago)
1662633479but the reported
minin facet response is
1662633500which is a little bit higher. Is there any chance this is being converted to float during the stats phase?
Kishore Nallan01:37 AM
Kishore Nallan01:11 PM
floatterm is used in the openapi spec so the impact to generated clients/consumers would be minor but it would probably need a ‘major’ version bump for semver sake
Indexed 2779 threads (79% resolved)
Resolving Floating Point Arithmetic in Facets
Claudiu reported an issue with floating point value representation in facets and found a workaround by converting everything to int32. Kishore Nallan validated this fix and also committed to finding a solution. Later, Erick faced a related error.
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.
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.