JSON object properties are not positional

[clintongormley]

Hiya

It looks like you are parsing JSON as a stream, where position matters, instead of parsing the whole objects before analysing them. For instance, this works:

curl -XGET 'http://127.0.0.2:9200/_all/_search'  -d '
{ query: 
    {
       "filteredQuery" : {
          "query" : {
             "term" : {
                "text" : "foo"
             }
          },
          "filter" : {
             "range" : {
                "num" : {
                   "from" : 10,
                   "to" : 20
                }
             }
          }
       }
   }
}
'

But this fails:
curl -XGET 'http://127.0.0.2:9200/_all/_search' -d '
{ query:
{
"filteredQuery" : {
"filter" : {
"range" : {
"num" : {
"to" : 20,
"from" : 10
}
}
},
"query" : {
"term" : {
"text" : "foo"
}
}
}
}
}
'

A JSON parser should consider these two structures to be identical, which is also the thing that rules out having non-unique property names.

thanks

Clint

(Edited to correct JSON)

[kimchy]

In all the places where JSON is handled, location is not relevant. This problem is not actually related to the location of the filter and the query (there is support for placing them where you want) but with the fact the range query did not behaved correctly when used as inner query.

I pushed a fix for it, can you give it a go?

[clintongormley]

Perfect! that works - thanks

[kimchy]

Great, closing.