This message was deleted.
# troubleshooting
s
This message was deleted.
g
it could be down to floating-point rounding
you could check this by doing, like,
m_criticality BETWEEN 0.3799 AND 0.3801
instead of
m_criticality = 0.38
and see if that is useful
g
Yes, it was down to rounding issue. When I give round(m_criticality, 2) <- this works. So like in other programming languages, the storage representation of float must be a approximation and not an exact. I am indexing this data to druid from parquet and that field calculation is already round( x, 2). So I did not expect this issue.