Hi, I have some doubts and suggestions for the same. Currently, we support these UDFs --> IN_POLYGON, IN_POLYGON_LIST, IN_POLYLINE_LIST, IN_POLYGON_RANGE_LIST but the user needs to give polygon input manually and as polygon can have many points, it is hard to give manually. So, your requirement is to give new UDF , IN_POLYGON_JOIN where polygon inputs are present in another table and you want to join with the main table.
*please find my doubts below* a. why to do join ? when you can form a subquery to query the polygons from table2 and give it as input for IN_POLYGON UDF and other existing UDFs b. no need to support the same for IN_POLYLINE_LIST and IN_POLYGON_RANGE_LIST UDF also ? *Suggestions:* a. Table names and queries are not matching, please update b. The query doesn't look like the union query as explained in the diagram, please update and explain c. Please consider some sample data with examples for t1 and t2. Also, provide the expected query result also d. Also mention, how to select data from single polygon and multi polygon from the tables. Thanks, Ajantha On Tue, Mar 30, 2021 at 11:25 AM Kunal Kapoor <[email protected]> wrote: > +1 > > On Mon, Mar 22, 2021 at 4:07 PM Indhumathi <[email protected]> > wrote: > > > Hi community, > > > > Currently, carbon supports IN_POLYGON and IN_POLYGON_LIST udf's, > > where user has to manually provide the polygon points(series of latitude > > and longitude pair), to query carbon table based on spatial index. > > > > This feature will support JOIN tables based on IN_POLYGON udf > > filter, where polygon data exists in a table. > > > > Please find below link of design doc. Please check and give > > your inputs/suggestions. > > > > > > > https://docs.google.com/document/d/11PnotaAiEJQK_QvKsHznDy1I9tO4idflW32LstwcLhc/edit#heading=h.yh6qp815dh3p > > > > > > Thanks & Regards, > > Indhumathi M > > > > > > > > -- > > Sent from: > > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ > > >
