hey I was trying to use geoindex feature in pinot....
# general
c
hey I was trying to use geoindex feature in pinot. but seems the index doesn’t apply because the
numEntriesScannedInFilter
. is high (equals to the number of docs). the pinot version is
0.8.0
. the query is
Copy code
select count(*) from some_table where  st_distance(resto_st_point, st_point(116.459717 , 39.955734, 1)) < 3000
the table config is
Copy code
"fieldConfigList": [
      {
        "name": "resto_st_point",
        "encodingType": "RAW",
        "indexType": "H3",
        "properties": {
          "resolutions": "12"
        }
      }
    ],
.....
      "noDictionaryColumns": [
        "resto_st_point"
      ],
and if i change the threshold to 300 (meters), the index hits.
m
@User ^^
y
check the query plan in trace mode and see why index is not in use
c
let me check.
is this the right trace:
Copy code
"0_0": [
        {
          "H3IndexFilterOperator Time": 0
        },
        {
          "RangeDocIdSetOperator Time": 0
        },
        {
          "ProjectionOperator Time": 0
        },
        {
          "RangeDocIdSetOperator Time": 0
        },
        {
          "ProjectionOperator Time": 0
        },
not sure how to interpret it.
and this is for meter is 300.
Copy code
{
          "H3IndexFilterOperator Time": 6
        },
        {
          "DocIdSetOperator Time": 6
        },
        {
          "ProjectionOperator Time": 6
        },
cc @User @User
y
That means the h3index operator is used
For both queries
c
oh.ok.
does it mean i didn’t setup resolution correct? for the first query (threshold is 3000 meters),
H3IndexFilterOperator Time
is always just
0
or
1
.
@User
y
whats the resolution did you use?
c
12
y
if resolution is too small, then you'll have lots of small indices
12 is 9m
too small
c
oh. I see. i understand it wrong. i thought the resolution is the bigger the faster.