# Compare condition use dot in JSON key string **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-alerting\ **Created:** [January 26, 2016, 6:46am UTC](https://discuss.elastic.co/t/compare-condition-use-dot-in-json-key-string/40089 "2016-01-26T06:46:48Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![chenryn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chenryn/32/44917_2.png) [@chenryn](https://discuss.elastic.co/u/chenryn)\ **Post date:** [January 26, 2016, 6:46am UTC](https://discuss.elastic.co/t/compare-condition-use-dot-in-json-key-string/40089/1 "2016-01-26T06:46:49Z")
Elasticsearch 2.x forbidden us using dot in JSON key strings. But the compare condition of watcher configuration always use dot, like `ctx. **`, `ctx.**.**`. It make us a confusion. ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [January 28, 2016, 9:46am UTC](https://discuss.elastic.co/t/compare-condition-use-dot-in-json-key-string/40089/2 "2016-01-28T09:46:00Z")
Hey, Elasticsearch 2.x forbids to use field names that contain dots, but it still requires you to use the dot-notation to refer to inner fields. See [https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking\_20\_mapping\_changes.html#\_field\_names\_may\_not\_contain\_dots](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_mapping_changes.html#_field_names_may_not_contain_dots) --Alex ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:47pm UTC](https://discuss.elastic.co/t/compare-condition-use-dot-in-json-key-string/40089/3 "2017-07-06T13:47:11Z")