What is the relationship of prestosql and prestodb?

[voycey]

I never see someone on other community channels so figured I would post here. We have been using Presto in production now for around a year and I only recently noticed this repository.

Could you please clarify what the relationship is between this one and prestodb/presto as both seem to be under active development and working?

Many thanks!

[martint]

This repository and github org were created shortly after the Presto Software Foundation was set up (see the original announcement: https://prweb.com/releases/prweb16070792.htm). It's where most of the committers to Presto and a much of the community are doing active development. Facebook continues to develop their version in the prestodb repository.

The new website is at https://prestosql.io, and you can find a link to the Slack channel under https://prestosql.io/community.html.

[voycey]

Thanks Martin,

I assume there is still a fair bit of collaboration between Facebook's Presto and the PSF? e.g. if FB develop some cool new functionality will it be ported across and vice versa?

Will the FB Presto backlog be used as part of the roadmap for this Presto?

[martint]

Unfortunately, we have very little visibility into what FB is doing and their plans for their version. We've been picking some changes and bug fixes that we've found interesting, but we expect that's going to be increasingly difficult as the code bases continue to diverge (e.g., prestosql has 500+ commits and more than half of those are not in the other repo).

Will the FB Presto backlog be used as part of the roadmap for this Presto?

The roadmap is being driven by what the community needs and is able to work on.

[vweevers]

Is FB Presto going to be phased out in favor of this fork? If not, could this project be renamed to avoid confusion?

[martint]

I can't speak for what FB intends to do with their project, but the original founders and the major contributors that are still active (who wrote the majority of the codebase) are developing on this repository. It's also the one supported by many Presto vendors such as Starburst, Qubole, TreasureData, Varada, etc, and has a large and growing community of users and contributors.

[vweevers]

Having read this thread and the PSF announcement, apologies, I'm still missing the why of the fork. Both have a dedicated GitHub org, both claim to be the official home of Presto, both had an equal amount of activity (and number of external contributors) in the past 30d.

Activity (click to expand)

prestodb/presto:

prestosql/presto:

If the reasons for the fork are private, due to internal friction, politics and/or commercial interests, I can understand that. But seeing as both projects are very much alive, I think it would help the larger community to give this a new distinctive name.

[findepi]

@vweevers I see where you are coming from. Yes, as the activity shows, both projects are active.
Please have a look at project contributors. You will find out that this is the Presto project we built over the years.
This is the same team, same people. In my opinion, renaming it would cause more confusion, more harm than good.

Also, this is the same community that gathered around the project over the time.
Join Presto Community Slack (https://prestosql.io/community.html) and the mailing group (you may also want to
join the old slack too). Wait a week or two and experience the community.

[vweevers]

@findepi Thank you.

One additional note, regarding the project description: people may read "Official home of the community version of Presto" as this being a "light" edition, as if there is also a paid Enterprise edition. Perhaps tweak that a bit.