Hi Bertil,
Let me explain a bit about Drill and Calcite. Drill uses Calcite for query
planning. Until fairly recently, Drill had a fork of Calcite that had some
special features which Drill required. However, about 1-2 versions ago, we
were able to get Drill off of the fork an onto "mainstr
Hi Jia,
Thanks for your interest! I'd be happy to work with you to build out a Drill
<> Sedona collab. This sounds really interesting and I think would be a great
addition to both projects.
With that said, I'm totally unfamiliar with Sedona unfortunately, so I'm not
sure how much help I can b
Hello Charles
Le 2024-02-01 à 23 h 43, Charles Givre a écrit :
I'd love for Drill to be included in this.
That would be great. You are welcome to add Drill in the wiki page at [1].
A while ago, I started work on a collection of UDFs for interacting
with H3 Geo Indexes. I'm not an expert on
No offence taken on my side ;-)
Do you think sedona-common could broaden its scope to non cluster technologies?
In Baremaps, we assumed that a few TBs of vector data can now easily be
processed efficiently on a single node with a lot of RAM and NVMe SSDs. Our
current implementation uses Postgis
Hi all (removing non-geospatial projects from the loop),
Just to clarify about the mission of the Apache Sedona project and make
sure nobody gets offended by my words before :-)
First of all, sedona-common is not a replacement of JTS at all. I also
contribute to JTS. Instead, sedona-common is mor
