does anybody know about this issue?
# community-helpc
Claudiu Roman Ardelean
05/19/2021, 7:40 PMdoes anybody know about this issue?
j
Jason Bosco
05/19/2021, 8:18 PMAh good ol' floating point arithmetic. Could you open a github issue about this @Claudiu Roman Ardelean?
c
Claudiu Roman Ardelean
05/19/2021, 8:22 PMhey, i will tomorrow, in the document the value looks ok in the hits, just on the facets value is the problem
k
Kishore Nallan
05/21/2021, 10:03 AM@Claudiu Roman Ardelean I'm not able to reproduce this issue. I indexed a single document with a facet field value of
113.4Kishore Nallan
05/21/2021, 10:03 AMIf you can share a small snippet that reproduces this issue, that will help us narrow down the issue.
c
Claudiu Roman Ardelean
05/21/2021, 12:09 PMhey @Kishore Nallan but in the document the value of the field "points" is 113.4 and in the facet is returned as 113.400002. Why is this happening?
Claudiu Roman Ardelean
05/21/2021, 12:11 PMmessage has been deleted
k
Kishore Nallan
05/21/2021, 12:16 PM@Claudiu Roman Ardelean That's because many floating point numbers cannot be represented exactly, so when they are serialized they might have some trailing decimal places at the end. In general, for facets it is better to store price in cents (as integer) instead of a float.
Kishore Nallan
05/21/2021, 12:17 PMIn your original post though, you said that
113.4 is changed to 114.300003c
Claudiu Roman Ardelean
05/21/2021, 12:31 PMlook at the CB field 63.3 is returned in facet like 63.299999
Claudiu Roman Ardelean
05/21/2021, 12:33 PMthe thing is i have to do a filter in the sidebar, and i need the exact value
Claudiu Roman Ardelean
05/21/2021, 12:33 PMbecause i will filter by that value
Claudiu Roman Ardelean
05/21/2021, 12:33 PMa workaround is to convert everything to int32
k
Kishore Nallan
05/21/2021, 12:33 PMYes, it's the same issue. When you convert a number from a floating point representation to string, this can happen unless we know how many decimal places the original precision of the float was. In this case, the best way to work around this issue is to store the float as an integer in cents.
👍 1
c
Claudiu Roman Ardelean
05/21/2021, 12:34 PMthanks
Claudiu Roman Ardelean
05/21/2021, 12:34 PMlike i guessed
k
Kishore Nallan
05/21/2021, 12:35 PMIn the mean time, I will see if there is anything we can do here. It's a notoriously difficult problem because of the way a float is represented.
c
Claudiu Roman Ardelean
05/21/2021, 12:36 PMi understand
Claudiu Roman Ardelean
05/21/2021, 12:36 PMi will user. integer
k
Kishore Nallan
05/21/2021, 12:36 PM👍
c
Claudiu Roman Ardelean
05/21/2021, 12:37 PMyou are doing a good job
🙌 1
k
Kishore Nallan
05/21/2021, 1:28 PM@Claudiu Roman Ardelean Found a way to fix this. I can cut you a RC build where this is addressed, if you would like.
c
Claudiu Roman Ardelean
05/21/2021, 1:28 PMuh
Claudiu Roman Ardelean
05/21/2021, 1:28 PMi already used integer
Claudiu Roman Ardelean
05/21/2021, 1:28 PMbut i can test it
k
Kishore Nallan
05/21/2021, 1:28 PMNo worries, then! Just wanted to check 🙂
c
Claudiu Roman Ardelean
05/21/2021, 1:29 PMyou guys are so fast 😄
k
Kishore Nallan
05/21/2021, 1:29 PM😄
c
Claudiu Roman Ardelean
05/21/2021, 1:29 PMi hope this community is getting bigger and bigger
🚀 2
e
Erick Heredia
02/01/2022, 7:06 PMhey @Kishore Nallan, I'm getting the error `400: {"message": "Field
cost