Resolving Floating Point Arithmetic in Facets
TLDR 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.
2
1
1
May 19, 2021 (31 months ago)
Claudiu
07:40 PMJason
08:18 PMClaudiu
08:22 PMMay 21, 2021 (30 months ago)
Kishore Nallan
10:03 AM113.4
and facet on the same field during searching. See the screenshot: the response looks fine.Kishore Nallan
10:03 AMClaudiu
12:09 PMClaudiu
12:11 PMKishore Nallan
12:16 PMKishore Nallan
12:17 PM113.4 is changed to 114.300003
-> such a large difference should not happen. Was that a typo?Claudiu
12:31 PMClaudiu
12:33 PMClaudiu
12:33 PMClaudiu
12:33 PMKishore Nallan
12:33 PM1
Claudiu
12:34 PMClaudiu
12:34 PMKishore Nallan
12:35 PMClaudiu
12:36 PMClaudiu
12:36 PMKishore Nallan
12:36 PMClaudiu
12:37 PM1
Kishore Nallan
01:28 PMClaudiu
01:28 PMClaudiu
01:28 PMClaudiu
01:28 PMKishore Nallan
01:28 PMClaudiu
01:29 PMKishore Nallan
01:29 PMClaudiu
01:29 PM2
Feb 01, 2022 (21 months ago)
Erick
07:06 PM400: {"message": "Field
cost should be a string or a string array."}
. The actual value is float. What do you think is the issue here?Typesense
Indexed 2786 threads (79% resolved)
Similar Threads
Resolving Float Value Issues in PHP and Typesense.
Zildjian was having issues with float values being treated as int64 in Typesense. Kishore Nallan identified and rectified the issue, guiding the user through a software upgrade process.
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.
Issue with Dynamic Nested Field Type in TS Collection Schema
Justin encountered an issue with dynamic nested fields not showing as `float`. Jason suggested reproducing the error with a snippet, while Kishore Nallan was tagged for assistance.
Quick Retrieval of Min, Max, and Median Values from Search Query
Prajjval sought a more efficient way to find the min, max, and median values from a search query result. Jason suggested faceting. However, Prajjval clarified that faceting prolonged document upload due to a data type error, which was later resolved.
Precision Issues with Int64 Numeric Field in Go Client
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.