Hacker News Reader

Interesting, but why share the Sedona name?

I thought Apache Sedona is implemented in Java/Scala for distributed runtimes like Spark and Flink. Wouldn't Rust tooling for interactive use be built atop a completely different stack?

View on HN

It's built on a separate stack but conceptually it's very similar (DataFusion shares a number of idioms with Spark and has a number of projects implementing various Spark compatibility)...I think the idea was to bring the successful pieces of Sedona Spark to a wider audience.

Apache Sedona, not so well loved in the GIS space in my experience, so I don't think it's a huge issue even if it is a bit confusing.

Wait is this a sifferent.apache sedona to the spark based apache sedona GIS dataframe engine I've cone into contact with before?

Surely they're the same? Two sedona projects is one thing, but two apache sedona projects is sheer madness?

Yes, this is Apache SedonaDB and the other is just Apache Sedona (Spark)

Reply on news.ycombinator.com