Different behavior for incompatible type comparison between SQL++ and N1QL.

Different results between SQL++ and N1QL has been observed and analytics result is looking better wrt incompatible type comparisons.

In N1QL where the comparison hits incompatible type, it seems it is evaluated it to True while in analytics it is evaluated it to False.

Query: SELECT age FROM default where age > 1;

Analytics Output:

[

  {

    "age": 70

  },

{

    "age": 33

  },

  {

    "age": 12345.12345

  }

]

N1QL Output:

[

  {

    "age": 70

  },

{

    "age": 33

  },

  {

    "age": [

      1,

      2

    ]

  },

  {

    "age": {

      "key": "value"

    }

  },

  {

    "age": 12345.12345

  }

]