You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sedona.apache.org by Jia Yu <ji...@apache.org> on 2025/08/16 22:38:55 UTC
[DISCUSS] Sedona single-machine database query engine
Hi all,
As you know, one limitation of Sedona is that it must run on top of a
distributed query engine such as Apache Spark, Apache Flink, or Snowflake
to execute queries. This makes installation difficult and the overall user
experience and performance less than ideal. A few Sedona PMC members and
committers (Kristin, Furqaan, Feng, Pranav, and myself) have been thinking
about how we can make things easier for our users.
To address this, we’re exploring the idea of building a standalone
distributed database query engine designed specifically for geospatial
compute. We plan to start with a single-machine spatial database engine
that’s simple to install, easy to use, and delivers strong performance.
We’ve written some initial code in Rust, though it’s still at a very early
stage. Our goal is to create a dedicated repository and begin pushing
commits so we can gather community feedback and iterate together.
We’d love to hear your thoughts. If there are no objections, I’ll go ahead
and create a Sedona sub-repository named sedona-db.
Thanks,
Jia
Re: [DISCUSS] Sedona single-machine database query engine
Posted by Feng Zhang <fe...@apache.org>.
+1
On 2025/08/18 14:35:19 Matthew Powers wrote:
> +1 (non-binding).
>
> Exciting!!
>
> On Sat, Aug 16, 2025 at 6:39 PM Jia Yu <ji...@apache.org> wrote:
>
> > Hi all,
> >
> > As you know, one limitation of Sedona is that it must run on top of a
> > distributed query engine such as Apache Spark, Apache Flink, or Snowflake
> > to execute queries. This makes installation difficult and the overall user
> > experience and performance less than ideal. A few Sedona PMC members and
> > committers (Kristin, Furqaan, Feng, Pranav, and myself) have been thinking
> > about how we can make things easier for our users.
> >
> > To address this, we’re exploring the idea of building a standalone
> > distributed database query engine designed specifically for geospatial
> > compute. We plan to start with a single-machine spatial database engine
> > that’s simple to install, easy to use, and delivers strong performance.
> > We’ve written some initial code in Rust, though it’s still at a very early
> > stage. Our goal is to create a dedicated repository and begin pushing
> > commits so we can gather community feedback and iterate together.
> >
> > We’d love to hear your thoughts. If there are no objections, I’ll go ahead
> > and create a Sedona sub-repository named sedona-db.
> >
> > Thanks,
> > Jia
> >
>
Re: [DISCUSS] Sedona single-machine database query engine
Posted by Matthew Powers <ma...@gmail.com>.
+1 (non-binding).
Exciting!!
On Sat, Aug 16, 2025 at 6:39 PM Jia Yu <ji...@apache.org> wrote:
> Hi all,
>
> As you know, one limitation of Sedona is that it must run on top of a
> distributed query engine such as Apache Spark, Apache Flink, or Snowflake
> to execute queries. This makes installation difficult and the overall user
> experience and performance less than ideal. A few Sedona PMC members and
> committers (Kristin, Furqaan, Feng, Pranav, and myself) have been thinking
> about how we can make things easier for our users.
>
> To address this, we’re exploring the idea of building a standalone
> distributed database query engine designed specifically for geospatial
> compute. We plan to start with a single-machine spatial database engine
> that’s simple to install, easy to use, and delivers strong performance.
> We’ve written some initial code in Rust, though it’s still at a very early
> stage. Our goal is to create a dedicated repository and begin pushing
> commits so we can gather community feedback and iterate together.
>
> We’d love to hear your thoughts. If there are no objections, I’ll go ahead
> and create a Sedona sub-repository named sedona-db.
>
> Thanks,
> Jia
>
Re: [DISCUSS] Sedona single-machine database query engine
Posted by Jia Yu <ji...@apache.org>.
Hi all,
Thanks for the support. I will create a repo sedona-db!
Jia
On Tue, Aug 19, 2025 at 8:43 AM Dewey Dunnington <de...@gmail.com>
wrote:
> Thank you for starting this discussion! I agree that creating a repository
> to ensure the IP of our experiments is tracked is a great idea. +1!
> (non-binding)
>
> On Mon, Aug 18, 2025 at 6:13 PM Furqaan Khan <fu...@apache.org> wrote:
>
> > +1 excited for this development!!
> >
> > On Mon, Aug 18, 2025 at 11:22 AM Feng Zhang <fe...@apache.org>
> wrote:
> >
> > > +1
> > >
> > > On 2025/08/16 22:38:55 Jia Yu wrote:
> > > > Hi all,
> > > >
> > > > As you know, one limitation of Sedona is that it must run on top of a
> > > > distributed query engine such as Apache Spark, Apache Flink, or
> > Snowflake
> > > > to execute queries. This makes installation difficult and the overall
> > > user
> > > > experience and performance less than ideal. A few Sedona PMC members
> > and
> > > > committers (Kristin, Furqaan, Feng, Pranav, and myself) have been
> > > thinking
> > > > about how we can make things easier for our users.
> > > >
> > > > To address this, we’re exploring the idea of building a standalone
> > > > distributed database query engine designed specifically for
> geospatial
> > > > compute. We plan to start with a single-machine spatial database
> engine
> > > > that’s simple to install, easy to use, and delivers strong
> performance.
> > > > We’ve written some initial code in Rust, though it’s still at a very
> > > early
> > > > stage. Our goal is to create a dedicated repository and begin pushing
> > > > commits so we can gather community feedback and iterate together.
> > > >
> > > > We’d love to hear your thoughts. If there are no objections, I’ll go
> > > ahead
> > > > and create a Sedona sub-repository named sedona-db.
> > > >
> > > > Thanks,
> > > > Jia
> > > >
> > >
> >
>
Re: [DISCUSS] Sedona single-machine database query engine
Posted by Dewey Dunnington <de...@gmail.com>.
Thank you for starting this discussion! I agree that creating a repository
to ensure the IP of our experiments is tracked is a great idea. +1!
(non-binding)
On Mon, Aug 18, 2025 at 6:13 PM Furqaan Khan <fu...@apache.org> wrote:
> +1 excited for this development!!
>
> On Mon, Aug 18, 2025 at 11:22 AM Feng Zhang <fe...@apache.org> wrote:
>
> > +1
> >
> > On 2025/08/16 22:38:55 Jia Yu wrote:
> > > Hi all,
> > >
> > > As you know, one limitation of Sedona is that it must run on top of a
> > > distributed query engine such as Apache Spark, Apache Flink, or
> Snowflake
> > > to execute queries. This makes installation difficult and the overall
> > user
> > > experience and performance less than ideal. A few Sedona PMC members
> and
> > > committers (Kristin, Furqaan, Feng, Pranav, and myself) have been
> > thinking
> > > about how we can make things easier for our users.
> > >
> > > To address this, we’re exploring the idea of building a standalone
> > > distributed database query engine designed specifically for geospatial
> > > compute. We plan to start with a single-machine spatial database engine
> > > that’s simple to install, easy to use, and delivers strong performance.
> > > We’ve written some initial code in Rust, though it’s still at a very
> > early
> > > stage. Our goal is to create a dedicated repository and begin pushing
> > > commits so we can gather community feedback and iterate together.
> > >
> > > We’d love to hear your thoughts. If there are no objections, I’ll go
> > ahead
> > > and create a Sedona sub-repository named sedona-db.
> > >
> > > Thanks,
> > > Jia
> > >
> >
>
Re: [DISCUSS] Sedona single-machine database query engine
Posted by Furqaan Khan <fu...@apache.org>.
+1 excited for this development!!
On Mon, Aug 18, 2025 at 11:22 AM Feng Zhang <fe...@apache.org> wrote:
> +1
>
> On 2025/08/16 22:38:55 Jia Yu wrote:
> > Hi all,
> >
> > As you know, one limitation of Sedona is that it must run on top of a
> > distributed query engine such as Apache Spark, Apache Flink, or Snowflake
> > to execute queries. This makes installation difficult and the overall
> user
> > experience and performance less than ideal. A few Sedona PMC members and
> > committers (Kristin, Furqaan, Feng, Pranav, and myself) have been
> thinking
> > about how we can make things easier for our users.
> >
> > To address this, we’re exploring the idea of building a standalone
> > distributed database query engine designed specifically for geospatial
> > compute. We plan to start with a single-machine spatial database engine
> > that’s simple to install, easy to use, and delivers strong performance.
> > We’ve written some initial code in Rust, though it’s still at a very
> early
> > stage. Our goal is to create a dedicated repository and begin pushing
> > commits so we can gather community feedback and iterate together.
> >
> > We’d love to hear your thoughts. If there are no objections, I’ll go
> ahead
> > and create a Sedona sub-repository named sedona-db.
> >
> > Thanks,
> > Jia
> >
>
Re: [DISCUSS] Sedona single-machine database query engine
Posted by Feng Zhang <fe...@apache.org>.
+1
On 2025/08/16 22:38:55 Jia Yu wrote:
> Hi all,
>
> As you know, one limitation of Sedona is that it must run on top of a
> distributed query engine such as Apache Spark, Apache Flink, or Snowflake
> to execute queries. This makes installation difficult and the overall user
> experience and performance less than ideal. A few Sedona PMC members and
> committers (Kristin, Furqaan, Feng, Pranav, and myself) have been thinking
> about how we can make things easier for our users.
>
> To address this, we’re exploring the idea of building a standalone
> distributed database query engine designed specifically for geospatial
> compute. We plan to start with a single-machine spatial database engine
> that’s simple to install, easy to use, and delivers strong performance.
> We’ve written some initial code in Rust, though it’s still at a very early
> stage. Our goal is to create a dedicated repository and begin pushing
> commits so we can gather community feedback and iterate together.
>
> We’d love to hear your thoughts. If there are no objections, I’ll go ahead
> and create a Sedona sub-repository named sedona-db.
>
> Thanks,
> Jia
>