Ross ROSS = Recommend OSS · open-source software intelligence for agents

apache/calcite

Apache Calcite observed · 2026-08-28

github.com/apache/calcite · homepage · Java · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

77/100

  • Activity 99
  • Release rhythm 35
  • Longevity 100

Flags: no_releases

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 4452
  • days_rel: n/a
  • days_push: 7
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

5175 stars · 2515 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Apache Calcite is a dynamic data management framework for the JVM that supplies the building blocks of a database—an industry-standard SQL parser and validator, a customizable cost-based query optimizer, and logical/physical relational algebra—while deliberately omitting storage primitives. Through pluggable schema adapters and a JDBC driver, it lets applications execute SQL over heterogeneous data sources such as Cassandra, Elasticsearch, MongoDB, Kafka, Druid, and plain JDBC databases.

Use cases

  • parse and validate SQL queries in a Java application
  • run SQL queries over MongoDB, Elasticsearch, or other non-SQL data stores
  • build a custom database or query engine without writing a parser or optimizer from scratch
  • federate SQL queries across multiple heterogeneous data sources
  • convert SQL statements into relational algebra and back
  • add rule-based query optimization and materialized view rewriting to a data system
  • expose a JDBC interface over custom schemas or in-memory data

When to choose

  • You are building a database, SQL layer, or query engine on the JVM and want proven parsing, planning, and optimization machinery
  • You need to present non-SQL data sources as queryable SQL tables with minimal configuration
  • You want a highly extensible optimizer with pluggable rules, cost models, and relational operators
  • You need data virtualization or SQL federation across diverse backends

When to avoid

  • You need a ready-to-run database that actually stores and processes data—Calcite intentionally omits storage and data processing
  • Your stack is not JVM-based, since Calcite is a Java library
  • You only need simple embedded analytics where a full database would be simpler than embedding a query framework

Facets

framework · maturity stable

parser database compiler middleware databases big-data analytics jvm windows cross-platform sql-parser query-optimizer jdbc-driver relational-algebra data-virtualization query-federation materialized-views pluggable-adapters sql-dialect query-planning data-engineering linux macos

7 sources

Member repositories

RepositoryRoleHealth v2
apache/calcitemain77

For agents

markdown · JSON · MCP: product_card(name="apache/calcite")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem