Born at LinkedIn and Uber, Pinot serves user-facing analytics at sub-second latency. DbSchema connects through the Pinot JDBC driver and lays those table schemas out visually — no more reading schema JSON to learn what a table contains.
Trusted by teams at
Pinot feeds analytics that customers see, so a schema mismatch is a public bug. Yet each table's structure hides in its own schema JSON, and the offline and real-time variants of the same data evolve on separate paths.
DbSchema puts both variants on one canvas, where a drifted column stands out at a glance instead of surfacing in a dashboard.
Check the schema in DbSchema before your users check the dashboard.
Lay offline and real-time schemas next to each other, annotate index configurations, and spot structural drift before it breaks a query.
Pick columns, filters, and grouping in the visual builder and inspect the generated SQL — a faster path to a first cut of a dashboard query.
Author GROUP BY, HAVING, and DATETIMECONVERT statements with table and column completion, and page through large OLAP result sets in the grid.
Generate HTML or PDF documentation of your Pinot tables — columns, types, and the index hints recorded on the layout — straight from what DbSchema introspected. New data engineers learn the model from a browsable reference, not from a directory of JSON files.
Register the Pinot JDBC driver
(org.apache.pinot.client.PinotDriver) from the Apache Pinot releases in DbSchema's
driver manager, then connect with jdbc:pinot://localhost:9000 — replacing
localhost with your cluster's hostname or load-balancer address. For TLS-enabled
clusters, switch to the https scheme and supply the certificate configuration;
further authentication depends on your deployment. Once connected, DbSchema lists every table
visible to the authenticated user.
Grab the free build — no signup — and evaluate the Architect tier for 15 days.
Teams working with Apache Pinot often use these engines too. Explore dedicated guides and JDBC setup for each.