HBase stores wide-column data on HDFS; Apache Phoenix layers SQL on top of it. DbSchema connects through the Phoenix JDBC driver and turns the Phoenix-managed schema into a browsable structure — column families, typed columns, and row data included.
UNSIGNED_INT and VARBINARYTrusted by teams at
A billion-row HBase table is organized by row keys and column families, and the shell
describes it one describe command at a time. What the data actually looks
like — which columns, which types, which family — stays tribal knowledge.
Phoenix exposes those column families as a typed SQL schema, and DbSchema reads it into a structured view your whole engineering team can browse, query, and document.
Desktop tooling for the parts of HBase the shell makes hard.
DbSchema reads the Phoenix-managed schema and shows each table's column families with the full data type catalog per column — no HBase shell session needed.
Compose SELECT statements by picking tables and predicates; Phoenix translates them into efficient row key scans, so queries stay fast without scan-mechanics expertise.
Fetch rows from wide tables into a paginated grid, apply column filters, and inspect individual cell values without constructing scan operations by hand.
Most people who need to understand the data model should never hold cluster credentials. DbSchema exports the Phoenix-managed schema as interactive HTML5 documentation — diagrams, tables, and column details that open in a browser, far away from ZooKeeper.
Explore the Documentation Tool
HBase has no JDBC endpoint of its own — Apache Phoenix supplies the SQL layer, and part of Phoenix runs inside the HBase cluster. The Phoenix client jars are not bundled with DbSchema: register them in the Driver Manager as described on the HBase JDBC driver page.
The URL points at the ZooKeeper quorum, not at an HBase port:
jdbc:phoenix:zookeeper_host:2181:/hbase, with 2181 as ZooKeeper's default. The
Phoenix thin client is an alternative, and requires a running Phoenix Query Server. On Amazon
EMR, take the ZooKeeper address from the cluster summary page and let the security group accept
inbound traffic on port 2181 before connecting.
The installer includes the free Community Edition plus a 15-day Architect trial.
Teams working with Apache HBase often use these engines too. Explore dedicated guides and JDBC setup for each.