You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Geometry type is already available in PrestoDB. Incorporating a similar type in Velox would align it with modern requirements for geospatial analytics.
To achieve this, I plan to add GeometryType as a custom type in Prestissimo and incrementally introduce new UDFs. The tasks can be divided into multiple PRs:
Add the Geometry type and tests.
Introduce the necessary library dependency (e.g., GEOS) for geometry manipulation.
Implement serialization and deserialization logic for the Geometry type and add tests.
Add relevant UDFs (e.g. st_contains) for the geometry type and register them.
Looking forward to feedback and suggestions!
The text was updated successfully, but these errors were encountered:
Introduce the necessary library dependency (e.g., GEOS) for geometry manipulation.
Ideally these should be optional imo. Could we add this as an modular, optional component (see storage_adapters wrt not leaking dependencies etc.).
Not sure if this is possible in Velox from a technical perspective (e.g. similar to extension types in arrow) or if it is more akin to change to the arrow spec (e.g. ListView etc.)?
Description
The Geometry type is already available in PrestoDB. Incorporating a similar type in Velox would align it with modern requirements for geospatial analytics.
To achieve this, I plan to add
GeometryType
as a custom type in Prestissimo and incrementally introduce new UDFs. The tasks can be divided into multiple PRs:st_contains
) for the geometry type and register them.Looking forward to feedback and suggestions!
The text was updated successfully, but these errors were encountered: