WangCHX commented on PR #8620: URL: https://github.com/apache/pinot/pull/8620#issuecomment-1116762409
> > > This is not the correct fix. The filter operator relies on the H3 index on the column. If the column is within an expression, the result will be wrong. E.g. `ST_DISTANCE(geoCol, 'point')` is not the same as `ST_DISTANCE(myFunc(geoCol), 'point')`, and we cannot use the same index because the index is not applied to the `myFunc(geoCol)` > > > > > > is it ok for me to add constraints that the function only can be `toSphericalGeography` and `toGeometry` right now? > > Why do you need to do `toSphericalGeography` or `toGeometry` on a column with H3 index? IIUC, H3 index implies the underlying points are geography, and `ST_DISTANCE(toGeometry(geoCol), 'point')` should not use H3 index. I think the underlying is a point. H3 index only take coordinate. so it can be applied to both geography and geometry. Also [ST_Contains](https://docs.pinot.apache.org/configuration-reference/functions/stcontains) only can be applied to `Geometry`. If i want to use ST_DISTANCE and ST_Contains at the same time, seems I need to create two columns. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
