# Integer comparison not working **URL:** \ **Category:** Logstash\ **Created:** [July 22, 2020, 8:50pm UTC](https://discuss.elastic.co/t/integer-comparison-not-working/242248 "2020-07-22T20:50:33Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Jenni](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jenni/32/29684_2.png) [@Jenni](https://discuss.elastic.co/u/Jenni)\ **Post date:** [July 23, 2020, 3:35am UTC](https://discuss.elastic.co/t/integer-comparison-not-working/242248/4 "2020-07-23T03:35:39Z")
Here's a quite recent discussion on that topic: > [@When to use "Object" field datatype vs flat fieldnames](https://discuss.elastic.co/t/when-to-use-object-field-datatype-vs-flat-fieldnames/217687/2): > > In this context, think of JSON objects as namespaces. Related information gets stored under a common root, which makes it easier for humans to identify which bits of the data belong together. Functionally and performance-wise these 3 are equivalent: "source\_ip": "10.20.30.40" "source.ip": "10.20.30.40" "source": { "ip": "10.20.30.40"} The 3rd option groups the related fields in the \_source of a document and makes it easier to read, IMO. --- _[View the full topic](https://discuss.elastic.co/t/integer-comparison-not-working/242248)._