uber/aresdb

Geo intersection behaves incorrectly when number of points * number of rows is too big.

lucafuji opened this issue · 0 comments

Describe the bug
Geo intersection behaves incorrectly when number of points * number of rows is too big.
When adding more geos, the result size decreases.

To Reproduce
query:
use the following query

{
  "queries": [
    {
      "dimensions": [
        {
          "sqlExpression": "trips.request_at",
          "timeBucketizer": "day",
          "timeUnit" :"second"
        }
      ],
      "joins": [
        {
          "alias": "g",
          "table": "geofences_configstore_udr_geofences",
          "conditions": [
            "geography_intersects(g.shape, request_point)"
          ]
        }
      ],
      "measures": [
        {
          "sqlExpression": "count(*)"
        }
      ],
      "rowFilters": [
        "status = 'completed'",
        "g.geofence_uuid IN (0x2370A118017844258B5B0CA2AA24058A, 0x451F86CC12A543F4B3F795F247B6EF21, 0xAAE54A49FC1D43E0BB138F0AA2D0F28B, 0x7F9935CD9620475BA388E37194CE9AF6, 0xC2936F2AACAB4A2C936DCE75E23876A4)"
      ],
      "table": "trips",
      "timeFilter": {
        "column": "request_at",
        "from": "-7d",
        "to": "now"
      }
    }
  ]
}

Expected behavior
Count should increase after adding more geos.