Posted by
Ajantha Bhat on
Dec 17, 2020; 2:31pm
URL: http://apache-carbondata-dev-mailing-list-archive.168.s1.nabble.com/DISCUSSION-Geo-spatial-index-algorithm-improvement-and-UDFs-enhancement-tp104717p104897.html
Hi Shen Jiayu,
It is an interesting feature, thanks for proposing this.
+1 from my side for high-level design,
I have few suggestions and questions.
a) Better to separate new UDF, utility UDF PR from algorithm improvement PR
for ease of review and maintainability.
b) Union, intersection, and diff of polygons can be computed during the
filter expression creation and can send the final polygon coordinates as
one range filter to carbon.
c) About algorithm improvement, I saw that you have removed a few
parameters like ‘minLongitude’, ‘maxLongitude’, ‘minLatitude’,
‘maxLatitude’. Anything else changed, can you describe more about what kind
of changes done to improve the algorithm?
d) Please capture the performance results due to algorithm changes with and
without these changes.
e) You have also mentioned supporting Geohash column from user during load.
This case no need to configure any spatial index properties in table
properties right ?
Thanks,
Ajantha
On Mon, Dec 14, 2020 at 9:18 PM haomarch <
[hidden email]> wrote: