By default all Cloudfront fields are uploaded as strings, meaning in Elasticsearch you're unable to use operations such as between, greater than, sum, average, etc on those numeric fields.
I reference each field by name as this is quicker, but could alternatively try to be clever and identify numeric fields based on their contents, but expect that this would be slower.
Coverage remained the same at 100.0% when pulling fda3fc74c3d110c625d46f77583b8fd06c829ddc on PeteLawrence:master into 729f9ba9c8cf8e7cda6e0f69d38cafb61800e8d8 on arithmetric:master.
Coverage remained the same at 100.0% when pulling 4b240aa56048e10660dc45da7f02369ff228e146 on PeteLawrence:master into 20705f50d5a19ec00023ab4d37ef4a701a18c970 on arithmetric:master.
Hi,
By default all Cloudfront fields are uploaded as strings, meaning in Elasticsearch you're unable to use operations such as between, greater than, sum, average, etc on those numeric fields.
I reference each field by name as this is quicker, but could alternatively try to be clever and identify numeric fields based on their contents, but expect that this would be slower.