I've recently noticed that a field I had declared as a scaled float is now a float. I'm not sure how this happened, but my guess is that elasticsearch did it automatically when a value that exceeded the precision was indexed: is this possible?
33degrees (Mateo) #1
33degrees (Mateo) #2
There's another field that was supposed to be a long that is now an int. Very confusing.
system (system) #3
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.