zetasql VS Apache Calcite

Compare zetasql vs Apache Calcite and see what are their differences.

Our great sponsors
  • JetBrains Dev Survey - What’s up with the C++ ecosystem in 2023?
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • Onboard AI - ChatGPT with full context of any GitHub repo.
  • WorkOS - The modern API for authentication & user identity.
zetasql Apache Calcite
15 28
2,089 4,257
0.9% 2.1%
0.0 9.0
4 months ago 4 days ago
C++ Java
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of zetasql. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-11-26.

Apache Calcite

Posts with mentions or reviews of Apache Calcite. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-26.
  • Data diffs: Algorithms for explaining what changed in a dataset (2022)
    8 projects | news.ycombinator.com | 26 Jul 2023
    > Make diff work on more than just SQLite.

    Another way of doing this that I've been wanting to do for a while is to implement the DIFF operator in Apache Calcite[0]. Using Calcite, DIFF could be implemented as rewrite rules to generate the appropriate SQL to be directly executed against the database or the DIFF operator can be implemented outside of the database (which the original paper shows is more efficient).

    [0] https://calcite.apache.org/

  • Apache Baremaps: online maps toolkit
    6 projects | news.ycombinator.com | 28 May 2023
    Yes, planetiler rocks and the memory mapped collections enabled us to remove our dependency to rocksdb.

    From my perspective, planetiler started as an effort to generate vector tiles from the OpenMapTile schema as fast as possible (pbf -> mvt). By contrast, Baremaps started as an effort to create a new schema and style from the ground up. In this regard, having a database (pbf -> db <- mvt) enables to live reload changes made in the configuration files. The database has a cost, but also comes with additional advantages (updates, dynamic data, generation of tiles at zoom levels 16+, etc.).

    That being said, I think the two projects overlap and I hope we will find opportunities to collaborate in the future. For instance, whereas PostgreSQL is still required in Baremaps, I recently ported a lot of the ST_ function of Postgis to Apache Calcite with the intent to execute SQL on fast memory mapped collection.


    A planet wide import in Postgis currently takes about 4 hours with the COPY API (easy to parallelize) followed by about 12 hours of simplification in Postgis (not easy to parallelize). I will try to publish a detailed benchmark in the future.

  • How to manipulate SQL string programmatically?
    2 projects | /r/dataengineering | 28 Apr 2023
    Use a SQL Parser like sqlglot or Apache Calcite to compile user's query into an AST.
  • Can SQL be used without an RDBMS?
    7 projects | /r/PHP | 27 Feb 2023
  • Want to contribute more to open source projects.
    8 projects | /r/dotnet | 18 Aug 2022
  • Postgres wire compatible SQLite proxy
    14 projects | news.ycombinator.com | 31 Mar 2022
    Awesome to see work in the DB wire compatible space. On the MySQL side, there was MySQL Proxy (https://github.com/mysql/mysql-proxy), which was scriptable with Lua, with which you could create your own MySQL wire compatible connections. Unfortunately it appears to have been abandoned by Oracle and IIRC doesn't work with 5.7 and beyond. I used it in the past to hack together a MySQL wire adapter for Interana (https://scuba.io/).

    I guess these days the best approach for connecting arbitrary data sources to existing drivers, at least for OLAP, is Apache Calcite (https://calcite.apache.org/). Unfortunately that feels a little more involved.

  • Launch HN: Hydra (YC W22) – Query Any Database via Postgres
    4 projects | news.ycombinator.com | 23 Feb 2022
    For anyone interested, Apache Calcite[0] is an open source data management framework which seems to do many of the same things that Hydra claims to do, but taking a different approach. Operating as a Java library, Calcite contains "adapters" to many different data sources from existing JDBC connectors to Elasticsearch to Cassandra. All of these different data sources can be joined together as desired. Calcite also has it's own optimizer which is able to push down relevant parts of the query to the different data sources. However, you get full SQL on data sources which don't support it, with Calcite executing the remaining bits itself.

    Unfortunately, I would not be too surprised if Calcite was found to be less performance-optimized than Hydra. That said, there are users of Calcite at Google, Uber, Spotify, and others who have made great use of various parts of the framework.

    [0] https://calcite.apache.org/

  • Open Source SQL Parsers
    17 projects | dev.to | 8 Oct 2021
    There are multiple projects that maintain parsers for popular open source databases like MySQL and Postgres. For other open source databases, the grammar can be extracted from the open-source project. For commercial databases, the only option is to reverse engineer the complete grammar. There are SQL parser/optimizer platforms like Apache Calcite that help to reduce the effort to implement the SQL dialect of your choice.
  • Does Java have an open source package that can execute SQL on txt/csv?
    3 projects | /r/programming | 22 Sep 2021
    Yes. Apache Calcite can do that.
  • Memoization in Cost-based Optimizers
    2 projects | dev.to | 9 Jun 2021
    You may find a similar design in many production-grade heuristic optimizers. In our previous blog post about Presto, we discussed the Memo class that manages such references. In Apache Calcite, the heuristic optimizer HepPlanner models node references through the class HepRelVertex.

What are some alternatives?

When comparing zetasql and Apache Calcite you can also consider the following projects:

Trino - Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)

ANTLR - ANTLR (ANother Tool for Language Recognition) is a powerful parser generator for reading, processing, executing, or translating structured text or binary files.

Presto - The official home of the Presto distributed SQL query engine for big data

sqlparse - A non-validating SQL parser module for Python

JSqlParser - JSqlParser parses an SQL statement and translate it into a hierarchy of Java classes. The generated hierarchy can be navigated using the Visitor Pattern

Apache Spark - Apache Spark - A unified analytics engine for large-scale data processing

Apache Drill - Apache Drill is a distributed MPP query layer for self describing data

spring-data-jpa-mongodb-expressions - Use the MongoDB query language to query your relational database, typically from frontend.

pgsql-parser - PostgreSQL Query Parser for Node.js

Leaf - Distributed ID Generate Service